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
BCrawlabilityrobots.txt present, no sitemapREVIEW
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
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent:discobot
Disallow:/
User-agent: SOTScraper
Disallow: /
User-agent:*
Disallow: /images/
Disallow: /rss/
Disallow: /cdn/
Crawl-delay:1
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 & Recommendations136 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 Records2 A records, 16 ms lookupPASS
| A | 23.62.46.172, 23.62.46.179 |
| AAAA | — |
| CNAME | — |
| NS | eur2.akam.net, eur4.akam.net, eur5.akam.net, usc5.akam.net, usw1.akam.net, usw2.akam.net, ns1-62.akam.net, ns1-216.akam.net |
| MX | 5 smtpgwa.supremecourt.gov 10 smtpgwb.supremecourt.gov |
| TXT | SPF v=spf1 mx ~all _m2rkjw91sbms4ahabusm53x46i3gqwa _ypjapu6pdizvu6remr2mz0p6fb4q0e7 globalsign-domain-verification=BagOKdwHdiXbsSFEVZgpivKZGYSQ-cCF6WP4b6Ih1m |
| 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), 807 ms totalPASS
https://supremecourt.gov
759 ms · HTTP/1.1
https://www.supremecourt.gov/
49 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://supremecourt.gov | 301 | 759 ms | HTTP/1.1 | AkamaiGHost |
| 2 | https://www.supremecourt.gov/ | 200 | 49 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+Domain Intelligencesupremecourt.gov — via get.gov, 19 years old, hosted on AkamaiPASS
51 days
September 5, 2026
136 days
Issued by DigiCert Inc
19 years
Registered July 12, 2007
Enabled
Protects against DNS spoofing
Akamai
ASN AS20940
23.62.46.179
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