Skip to content
https://doc.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
9
6 PASS 3 REVIEW
B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • 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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: ORD)
Got: cf-ray: 9f07366b5e93eb64-ORD
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f07366b5e93eb64-ORD
A+
DNS Records
4 A records, 55 ms lookup
PASS
4 A records, 55 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 172.65.90.24, 172.65.90.26, 172.65.90.27, 172.65.90.25
Info::
Has 4 IPv6 (AAAA) record(s)
Got: 2606:4700:78::90:0:183, 2606:4700:78::90:0:181, 2606:4700:78::90:0:180, 2606:4700:78::90:0:182
Info::
2 nameserver(s) configured
Got: cecelia.ns.cloudflare.com, max.ns.cloudflare.com
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: 55 ms
Got: 55 ms
A172.65.90.24, 172.65.90.26, 172.65.90.27, 172.65.90.25
AAAA2606:4700:78::90:0:183, 2606:4700:78::90:0:181, 2606:4700:78::90:0:180, 2606:4700:78::90:0:182
CNAME
NScecelia.ns.cloudflare.com, max.ns.cloudflare.com
MX
0 doc-gov.mail.protection.outlook.com
TXT
ms-domain-verification=63028525-11de-47e7-91a7-307726f4780a
00D8z0000008anh=1TBeq00000000cj
adobe-idp-site-verification=fe5d634e829422b4501772b53986053ec65bcd884c5db17dcdc5...
SPF v=spf1 include:spf.protection.outlook.com a:spf.servicenowservices.com ip4:208.1...
MS=ms91611337
CAALookup not available with standard resolver
Resolved in 55 ms

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
0 redirect(s), 469 ms total
PASS
0 redirect(s), 469 ms total

https://doc.gov

469 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://doc.gov403469 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:78::90:0:183, 2606:4700:78::90:0:181, 2606:4700:78::90:0:180, 2606:4700:78::90:0:182
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:78::90:0:183, 2606:4700:78::90:0:181, 2606:4700:78::90:0:180, 2606:4700:78::90:0:182 Connection Reachable (17 ms)
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.doc.gov/
200https://doc.gov/

HTTP → HTTPS

301http://doc.gov/ https://doc.gov/

Consistent

A+
Domain Intelligence
doc.gov — via get.gov, 28 years, 11 months old
PASS
doc.gov — via get.gov, 28 years, 11 months old
Info::
Domain registered until Aug 15, 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.
Domain expiry

29 days

August 15, 2026

SSL certificate

89 days

Issued by Google Trust Services

Domain age

28 years, 11 months

Registered October 2, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:78::90:0:183

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 August 15, 2026 (3 months)
Last Updated October 9, 2025
Name Servers cecelia.ns.cloudflare.com, max.ns.cloudflare.com
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2606:4700:78::90:0:183
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 521 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
51 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
333 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
520 ms
Total Time Total request time from DNS lookup through full response.
521 ms

Connection waterfall

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

Send Feedback