Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.
Learn more ▾ ▴
Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.
Source: RFC 8305 (Happy Eyeballs)
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain2 redirect(s), 531 ms totalREVIEW
https://nps.gov
474 ms · HTTP/1.1
https://www.nps.gov/
54 ms · HTTP/1.1
https://www.nps.gov/index.htm
2 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://nps.gov | 301 | 474 ms | HTTP/1.1 | Apache |
| 2 | https://www.nps.gov/ | 302 | 54 ms | HTTP/1.1 | CloudFront |
| 3 | https://www.nps.gov/index.htm | 200 | 2 ms | HTTP/1.1 | Apache |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
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
BTLS Certificate Expiry & Recommendations131 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- Add includeSubDomains to the HSTS directive
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records1 A records, 49 ms lookupPASS
| A | 52.6.8.53 |
| AAAA | 2600:9000:20aa:0:1:983:9400:93a1 |
| CNAME | — |
| NS | lucy.ns.cloudflare.com, ivan.ns.cloudflare.com |
| MX | 10 nps-gov.mail.protection.outlook.com |
| TXT | BEAA-1797-3015-58D3-FA87-9BD8-3ADE-179B SPF v=spf1 ip4:96.127.113.23 include:_spf.nps.gov include:servers.mcsv.net -all ueoq14l77f14ot5l94gnj8f73d _qbssbwgpkm46pn8gif4416ijhafqg85 adobe-sign-verification=ccc5d4bbde3e1c62a31238fd7983103730f30c32145a4ae2fe71264b... amazonses:72aXC5OVEkJqI109ds3EEaNByQb/SclYLq+pIp+JWz0= MS=ms12791101 334fjub5l60gouiv36ot0f4fr8 adobe-idp-site-verification=0c06fad3-cf1c-4e40-8ec6-2507879c946e k3x1fbzs2816tkxpg3c76qky6c7s2x4v |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+Crawlabilityrobots.txt present, sitemap with 6 URLsPASS
User-agent: *
Disallow: /ns/
Disallow: /search/
Disallow: /loader.cfm
Disallow: /*loader.cfm*
User-agent: bingbot
Crawl-delay: 5
Sitemap: https://www.nps.gov/sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencenps.gov — via get.gov, 28 years, 11 months oldPASS
46 days
August 29, 2026
131 days
Issued by DigiCert Inc
28 years, 11 months
Registered October 2, 1997
Enabled
Protects against DNS spoofing
Unknown
2600:9000:20aa:0:1:983:9400:93a1
get.gov
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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.
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