Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
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
HTTP → HTTPS
HTTP version does not redirect to HTTPS
BTLS Certificate Expiry & Recommendations235 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Add includeSubDomains to the HSTS directive
- 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, 33 ms lookupPASS
| A | 23.49.167.168 |
| AAAA | — |
| CNAME | — |
| NS | use1.akam.net, usw2.akam.net, ns1-139.akam.net, use5.akam.net, ns1-201.akam.net, use4.akam.net |
| MX | — |
| TXT | cisco-ci-domain-verification=520fae2bf78747a7b6c4a56b912d9e1f630981dd419617776bb... apple-domain-verification=0sMOLcD7LreOrRme SPF v=spf1 -all _6f81d8vkoxsoeq8xf67mqqn1x580dnl _a207fl5l20e7ou8ix07gghbuakx1s01 t20jdz1f1spnv2yr0ss3n58kk50mz5mp openai-domain-verification=dv-62U5tsgMaFbYuAxGrOJpCUtG _q0okt7qt847eqem9az5sfbf6oy3ptyc atlassian-domain-verification=nw6ZRLAkt1cc0uJY3t0ib4DY5ysWVws8HUwRo7dcHC9Ikjcn9n... adobe-idp-site-verification=cf4295727e27f91903cd8023af04d61380b76abfc95ebf0e0b9c... google-site-verification=_rTlqAXzTffwIunyQW6oJ9U0JJFi5UvFI2_-1ctsWeU _bsrn822l32tjquxrqyj94jexc5m6ko4 _98k6tw34p47j9tw9xq8nxe6yn3uzymq MS=ms88689177 box-domain-verification=aa977f32ea8c8bc09a1d794f3824e172d8a0f40fed162dc118beea41... google-site-verification=BHh7iUIbz0tIYBtRIXi9lO1em7ghqHaDbgx_8m-88lc _r9gndyvno2dtx5uygo59tbx46ilfboo _70idrfgocb533k99hccqav3vhnhw4bq |
| 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+Redirect Chain0 redirect(s), 90 ms totalPASS
https://senate.gov
90 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://senate.gov | 403 | 90 ms | HTTP/1.1 | AkamaiGHost |
A+Domain Intelligencesenate.gov — via get.gov, 28 years, 11 months old, hosted on AkamaiPASS
35 days
August 18, 2026
235 days
Issued by DigiCert Inc
28 years, 11 months
Registered October 2, 1997
Enabled
Protects against DNS spoofing
Akamai
ASN AS16625
23.49.167.168
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