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.
BTLS Certificate Expiry & Recommendations191 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
BCDN & DeliveryAkamaiREVIEW
A+DNS Records1 A records, 9 ms lookupPASS
| A | 23.222.18.169 |
| AAAA | 2a02:26f0:1180:187::447a, 2a02:26f0:1180:197::447a |
| CNAME | — |
| NS | asa.ns.cloudflare.com, tanner.ns.cloudflare.com |
| MX | 10 mxa-00376703.gslb.gpphosted.com 10 mxb-00376703.gslb.gpphosted.com |
| TXT | MS=ms47745217 1n25vm3j9qyl50w2lmtr07yrr1bb3j5f b7gyh2v0b9plxgbxj3f05984j8ydkc1r kzx864rmpgz2sqn611htwvpkjb2c4ybf sbh0ffwgs6dvnfl2c4rhp97r0g5qwq9y v=msv1t=67143E11-2ACB-4C50-9863-CFBD22611C10 google-site-verification=Yu0gqdoXIYSIgmTWo6_Z9E2tB5v9QKhPHwZeWbqphvo pm2hl6ylj1LvCcrU6dVoD5XchVrQyawQg/+bWKe1GEEhUIzAD4030jhU05DRWC5wrlBDofaT0uoOK+K7... SPF v=spf1 include:spf.dhs.gov include:spf.protection.outlook.com include:spf-003767... |
| 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.
ARedirect Chain1 redirect(s), 76 ms totalPASS
https://fema.gov
42 ms · HTTP/1.1
https://www.fema.gov/
34 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://fema.gov | 301 | 42 ms | HTTP/1.1 | AkamaiGHost |
| 2 | https://www.fema.gov/ | 403 | 34 ms | HTTP/1.1 | AkamaiGHost |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencefema.gov — via get.gov, 28 years, 11 months oldPASS
68 days
August 20, 2026
191 days
Issued by DigiCert Inc
28 years, 11 months
Registered October 2, 1997
Enabled
Protects against DNS spoofing
Unknown
2a02:26f0:1180:187::447a
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