Skip to content
https://opm.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Singapore, Singapore
302 Found
Checks
9
5 PASS 2 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 302 Expected: 301 redirect to HTTPS

www / non-www

200https://www.opm.gov/
200https://opm.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://opm.gov/ http://www.opm.gov/

HTTP version does not redirect to HTTPS

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
Crawlability
robots.txt present, sitemap with 21412 URLs
REVIEW
robots.txt present, sitemap with 21412 URLs
Info::
robots.txt is present
Got: 339 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Info::
sitemap.xml contains 21412 entries
Info::
robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

robots.txt 200 OK
Size 339 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *

Disallow: 


User-Agent: *

Disallow: /foia/quaterly/

Disallow: /Search

Disallow: https://apps.opm.gov/tax_calc/withhold_calc/index.cfm


Disallow: /*?forgotpassword=*

Disallow: /*&forgotpassword=*

Disallow: /*?dologin=*

Disallow: /*&dologin=*

Disallow: /*/print/


# Sitemaps

Sitemap: https://www.opm.gov/sitemap/
B
TLS Certificate Expiry & Recommendations
186 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

186
days left
0d 30d 60d 90d+

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 4 ms lookup
PASS
1 A records, 4 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.50.88.91
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:1413:5000:a81::174f, 2600:1413:5000:a8f::174f
Info::
6 nameserver(s) configured
Got: a1-12.akam.net, a5-67.akam.net, a11-67.akam.net, a14-64.akam.net, a18-65.akam.net, a20-66.akam.net
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 4 ms
Got: 4 ms
A23.50.88.91
AAAA2600:1413:5000:a81::174f, 2600:1413:5000:a8f::174f
CNAME
NSa1-12.akam.net, a5-67.akam.net, a11-67.akam.net, a14-64.akam.net, a18-65.akam.net, a20-66.akam.net
MX
0 opm-gov.mail.protection.outlook.com
TXT
MS=ms15252846
MS=ms35255137
tbcd7kxrzkw9py7sh6kksn5zfs19l4sy
google-gws-recovery-domain-verification=68398890
google-site-verification=V0UV_qinkHD_6nHDUzapyLVoTmouteKQPTusDqE_jrY
google-site-verification=j11qcer-IPY3hbU67y1N_994_x8fnLTlssDpyFRZIXU
7axh6RhNhWWjGH/6UD54HHrA3x0tNqHi2MGEN6MM/dyqbLwZqEnDkW+RndcBz2grhSSLNJ9qRSBXZxnU...
SPF v=spf1 ip4:205.131.184.50/32 ip4:205.131.184.51/32 ip4:205.131.184.52/32 ip4:205...
CAALookup not available with standard resolver
Resolved in 4 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 235 ms total
PASS
1 redirect(s), 235 ms total
Info::
Single redirect
Got: https://opm.gov → https://www.opm.gov/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://opm.gov

https://opm.gov

22 ms · HTTP/1.1

302

https://www.opm.gov/

213 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://opm.gov30222 msHTTP/1.1
2https://www.opm.gov/200213 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2600:1413:5000:a81::174f, 2600:1413:5000:a8f::174f
Got: 1 ms connect
IPv6 Ready
AAAA Records 2600:1413:5000:a81::174f, 2600:1413:5000:a8f::174f Connection Reachable (1 ms)
A+
Domain Intelligence
opm.gov — via get.gov, 28 years, 11 months old
PASS
opm.gov — via get.gov, 28 years, 11 months old
Info::
Domain registered until Sep 2, 2026 (4 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: get.gov
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Domain expiry

81 days

September 2, 2026

SSL certificate

186 days

Issued by DigiCert Inc

Domain age

28 years, 11 months

Registered October 2, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2600:1413:5000:a81::174f

Registrar

get.gov

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar get.gov
Created October 2, 1997 (28 years, 11 months ago)
Expires September 2, 2026 (4 months)
Last Updated November 26, 2025
Name Servers a1-12.akam.net, a11-67.akam.net, a14-64.akam.net, a18-65.akam.net, a20-66.akam.net, a5-67.akam.net
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2600:1413:5000:a81::174f
Data source: rdap (0.4s)

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 25 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
3 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
7 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
25 ms
Total Time Total request time from DNS lookup through full response.
26 ms

Connection waterfall

DNS Lookup 3 ms TCP Connect 1 ms TLS Handshake 7 ms Server Processing 14 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback