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
CURL VariantsActionwww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
BTLS Certificate Expiry & Recommendations89 days until leaf cert expires — 4 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 DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
BCDN & DeliveryVercelREVIEW
A+DNS Records2 A records, 48 ms lookupPASS
| A | 216.150.16.65, 216.150.1.65 |
| AAAA | — |
| CNAME | — |
| NS | bayan.ns.cloudflare.com, raquel.ns.cloudflare.com |
| MX | 1 smtp.google.com |
| TXT | MS=ms80611648 google-site-verification=dlMbde_meYAaYuf2md7Q_QFCRo0pbjynSkmaTwrsZmI SPF v=spf1 a include:_spf.google.com include:amazonses.com ~all google-site-verification=NxSdIQ-eGogL9Y-f2YwnsncRIxy_wYczgDj7Cc5MvUc google-site-verification=3uYwMdB1THNMju_HaMr9uFng1z8goAPx4-V0DHNdWuo |
| 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), 426 ms totalPASS
https://scotusblog.com
98 ms · HTTP/1.1
https://www.scotusblog.com/
328 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://scotusblog.com | 301 | 98 ms | HTTP/1.1 | Vercel |
| 2 | https://www.scotusblog.com/ | 200 | 328 ms | HTTP/1.1 | Vercel |
See the visual redirect chain in the HTTP Probe tab →
ACrawlabilityrobots.txt present, no sitemapPASS
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
User-Agent: *
Allow: /
Disallow: /api/
Disallow: /studio/
Disallow: /*?*q=
Disallow: /*?*topic=
Disallow: /*?*page=
User-Agent: GPTBot
Disallow: /
User-Agent: ChatGPT-User
Disallow: /
User-Agent: OAI-SearchBot
Disallow: /
User-Agent: ClaudeBot
Disallow: /
User-Agent: Claude-Web
Disallow: /
User-Agent: anthropic-ai
Disallow: /
User-Agent: CCBot
Disallow: /
User-Agent: Bytespider
Disallow: /
User-Agent: PerplexityBot
Disallow: /
User-Agent: Perplexity-User
Disallow: /
User-Agent: Amazonbot
Disallow: /
User-Agent: cohere-ai
Disallow: /
User-Agent: Diffbot
Disallow: /
User-Agent: Google-Extended
Disallow: /
User-Agent: FacebookBot
Disallow: /
User-Agent: Meta-ExternalAgent
Disallow: /
User-Agent: ImagesiftBot
Disallow: /
User-Agent: Applebot-Extended
Disallow: /
User-Agent: Timpibot
Disallow: /
User-Agent: YouBot
Disallow: /
User-Agent: Omgilibot
Disallow: /
User-Agent: Omgili
Disallow: /
User-Agent: ICC-Crawler
Disallow: /
User-Agent: DuckAssistBot
Disallow: /
Sitemap: https://www.scotusblog.com/sitemap.xml
No sitemap found
Adding a sitemap helps search engines discover your pages.
A+Domain Intelligencescotusblog.com — via Cloudflare, Inc., 21 years, 10 months old, hosted on AWSPASS
476 days
October 4, 2027
89 days
Issued by Let's Encrypt
21 years, 10 months
Registered October 4, 2004
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
216.150.1.65
Cloudflare, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033
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