Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BTLS Certificate Expiry & Recommendations54 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- 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 & DeliveryCloudflareREVIEW
A+DNS Records1 A records, 10 ms lookupPASS
| A | 160.79.104.10 |
| AAAA | 2607:6bc0::10 |
| CNAME | — |
| NS | isla.ns.cloudflare.com, randy.ns.cloudflare.com |
| MX | — |
| TXT | _4h91g65hky8g6rbfx22rpfu4pprn1v3 google-site-verification=NISbSmcIQumvbPjLbYAhRmzrx1LSAhRMH6XVaKTWxe0 google-site-verification=YPYhXirYOvYGGQtAypqom1k-1KMXKHeWbxKgw60bDfo google-site-verification=iDyYpE6uHVggWrWzK-MEosRSp7XUE7wqBLGX0Ua71Pc SPF v=spf1 -all |
| 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), 47 ms totalPASS
https://claude.ai
26 ms · HTTP/1.1
https://claude.ai/login
21 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://claude.ai | 302 | 26 ms | HTTP/1.1 | cloudflare |
| 2 | https://claude.ai/login | 200 | 21 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 11 URLsPASS
User-Agent: ia_archiver
Allow: /$
Allow: /login
Disallow: /
User-Agent: GPTBot
User-Agent: OAI-SearchBot
User-Agent: ChatGPT-User
Disallow: /
User-Agent: *
Disallow: /new?*
Disallow: /chat/*
Disallow: /share/*
Disallow: /magic-link*
Disallow: /api/*
Disallow: /onboarding*
Disallow: /upgrade*
Disallow: /lti/*
Disallow: /settings*
Disallow: /task*
Sitemap: https://claude.ai/sitemap.xml
- https://claude.ai/sitemaps/artifacts-be-...
- https://claude.ai/sitemaps/artifacts-be-...
- https://claude.ai/sitemaps/artifacts-cod...
- https://claude.ai/sitemaps/artifacts-dat...
- https://claude.ai/sitemaps/artifacts-lea...
- https://claude.ai/sitemaps/artifacts-lea...
- https://claude.ai/sitemaps/artifacts-lif...
- https://claude.ai/sitemaps/artifacts-lif...
- https://claude.ai/sitemaps/artifacts-lif...
- https://claude.ai/sitemaps/artifacts-pla...
- https://claude.ai/sitemaps/artifacts-tou...
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceclaude.ai — via MarkMonitor Inc., 7 years, 9 months oldPASS
1115 days
August 4, 2029
54 days
Issued by Let's Encrypt
7 years, 9 months
Registered August 4, 2018
Not enabled
Protects against DNS spoofing
Unknown
2607:6bc0::10
MarkMonitor 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