Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCrawlabilityno robots.txt, no sitemapREVIEW
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
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.
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
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations39 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- 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
BCDN & DeliveryCloudflareREVIEW
A+DNS Records2 A records, 7 ms lookupPASS
| A | 104.18.33.249, 172.64.154.7 |
| AAAA | 2a06:98c1:3103::ac40:9a07, 2a06:98c1:3105::6812:21f9 |
| CNAME | — |
| NS | art.ns.cloudflare.com, pat.ns.cloudflare.com |
| MX | 10 outmail01.federalreserve.gov 20 outmail02.federalreserve.gov |
| TXT | MS=ms94574649 dtm-domain-verification=k0gUuFsn78Ooxc4M6YT9MNez_SigrzKKGaoiedN_Vis cisco-ci-domain-verification=4341bc4bc4ab367a16c7ce7692e4842b57bce6243ebea679e71... SPF v=spf1 mx:frb.gov mx:abc.frb.gov a:zixmail.net a:smtpout.zixmail.com include:spf... |
| CAA | Lookup not available with standard resolver |
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.
ARedirect Chain1 redirect(s), 220 ms totalPASS
https://federalreserve.gov
22 ms · HTTP/1.1
https://www.federalreserve.gov/
198 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://federalreserve.gov | 301 | 22 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.federalreserve.gov/ | 200 | 198 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (2 ms)PASS
A+Domain Intelligencefederalreserve.gov — via get.gov, 28 years, 5 months oldPASS
79 days
September 2, 2026
39 days
Issued by Google Trust Services
28 years, 5 months
Registered April 2, 1998
Enabled
Protects against DNS spoofing
Unknown
2a06:98c1:3103::ac40:9a07
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