Skip to content
https://gpo.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
4 PASS 4 REVIEW 1 FIX
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
Redirect Chain
1 redirect(s), 1111 ms total
REVIEW
1 redirect(s), 1111 ms total
Info::
Single redirect
Got: https://gpo.gov → https://www.gpo.gov/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://gpo.gov
Warning::
Redirect overhead: 1111 ms total
Got: 1111 ms

https://gpo.gov

397 ms · HTTP/1.0

302

https://www.gpo.gov/

714 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://gpo.gov302397 msHTTP/1.0BigIP
2https://www.gpo.gov/200714 msHTTP/1.1cloudflare

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

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

C
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.gpo.gov/
200https://gpo.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://gpo.gov/ → https://www.gpo.gov/

Use 301 (permanent) instead of 302 (temporary)

B
TLS Certificate Expiry & Recommendations
309 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

309
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
  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 35 ms lookup
PASS
1 A records, 35 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 162.140.14.82
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns1.gpo.gov, ns2.gpo.gov
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: 35 ms
Got: 35 ms
A162.140.14.82
AAAA—
CNAME—
NSns1.gpo.gov, ns2.gpo.gov
MX
0 gpo-gov.mail.protection.outlook.com
TXT
sswc98trfnq947h6n2qxy0c8b4jtx16w
3ppq0glzx9jqptqm2vjr9408rrbj3bn4
adobe-idp-site-verification=ed70e46b8095ce3defd8cb71aee5597983f4c9c9d67ed30f18b7...
apple-domain-verification=5Ad1n20NuPa7cxbN
docker-verification=3c6296f4-c9d6-413d-95b3-1ed8783bc2d3
SPF v=spf1 ip4:18.224.245.68 ip4:162.140.252.206/31 ip4:162.140.64.208 ip4:162.140.2...
e8WTiTGmBS/5MCn4qp7AW4LAs2em2qIm/uuHvmohKPPP2ZtDr2v84+17NJ4txIiFyMo9KtIJoNkYKpj1...
mfbf4rwc5jtnw7wl7g6psmmkvt4jq0xb
google-site-verification=x9XWRvd7M4WwMKAnRdWtWJxv9SgzmKWpnQiTENZi8Lk
83lgxldchk5t2k83vkpb41tpvnl2p334
FveQ/soZoxZHlb+HOrJ9VLsSUa30XI8ortzCZQp3ZvzzW/dMT9oucMztwH/QslUP/l4aT/9Nk4/h+EXN...
CAALookup not available with standard resolver
Resolved in 35 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+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 124 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
Sitemap index with 1 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 124 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *



Sitemap: https://www.gpo.gov/sitemap/sitemap-index.xml

Sitemap: https://www.gpo.gov/sitemap/sitemap.gz
sitemap.xml 200 OK
Type Sitemap Index URLs 1 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
gpo.gov — via get.gov, 28 years, 11 months old, hosted on GPO-NET - U.S. Government Publishing Office, US
PASS
gpo.gov — via get.gov, 28 years, 11 months old, hosted on GPO-NET - U.S. Government Publishing Office, US
Info::
Domain registered until Jul 22, 2026 (3 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.
Info::
Hosting: GPO-NET - U.S. Government Publishing Office, US
Got: AS3705
Domain expiry

39 days

July 22, 2026

SSL certificate

309 days

Issued by DigiCert Inc

Domain age

28 years, 11 months

Registered October 2, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

GPO-NET - U.S. Government Publishing Office, US

ASN AS3705

162.140.14.82

Registrar

get.gov

Unlocked 2 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 July 22, 2026 (3 months)
Last Updated July 27, 2025
Name Servers ns1.gpo.gov, ns2.gpo.gov
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 162.140.14.82
ASN AS3705 (GPO-NET - U.S. Government Publishing Office, US)
Provider GPO-NET - U.S. Government Publishing Office, US
Data source: rdap (0.5s)

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 426 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
32 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
98 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
199 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
427 ms
Total Time Total request time from DNS lookup through full response.
427 ms

Connection waterfall

DNS Lookup 32 ms TCP Connect 98 ms TLS Handshake 199 ms Server Processing 98 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