Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.
Learn more ▾ ▴
Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.
Source: RFC 8305 (Happy Eyeballs)
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations81 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- 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
A+DNS Records2 A records, 16 ms lookupPASS
| A | 172.66.1.220, 162.159.141.224 |
| AAAA | 2a06:98c1:58::1d8, 2606:4700:7::1d8 |
| CNAME | — |
| NS | blue.foundationdns.com, blue.foundationdns.net, blue.foundationdns.org |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | MS=ms11638476 ZOOM_verify_od1bx9rWRyONZrEbyv0P4Q adobe-idp-site-verification=4d443bb146b2a60fc0c0216c899a6ef9baa971cc3c36ac4b3020... atlassian-domain-verification=uUTQHYge655RxaiCqp-IAyc/Q7GgtoJziDouyp0rB7n8OUdp4q... cursor-domain-verification-7hbr5z=RSrHsnGEmBu6asStY02YtbFpG docusign=d93b4318-1f4f-41da-b870-bdcd78c25e64 facebook-domain-verification=6z0y6uuhvh1uttqpr1r5xafmi95xe8 google-site-verification=8U7EQt5vjysnYK95n7JD8hHDaE7qtJgLbhoi_M5xIWw google-site-verification=8mIyQXp8D5O1sEUvWbPqBg9oB495DclpJBmDZWl-0is google-site-verification=b4AngDLH97k98MIXIFBsY1QwrRCnr16jB9bVtCnSpvo google-site-verification=eACr4LVWGfHC7y1ipVCq23EIOXVcSN2pP2ATg6xL9ps knowbe4-site-verification=fa92b9e4fa2fbe928824de444cebea5e openai-domain-verification=dv-avgJmtXY4qdIWzX5tkiKQnkI shopify-verification-code=jHrlSZnXOLH4fjtv3Pd55lawJWmh5H slack-domain-verification=MmS8dxt4px7zNS8yQvItWQHWf4Q67CeWQ7GszYle SPF v=spf1 include:spf.clearslide.com include:_spf.google.com include:_spf.createsen... windsurf-verification=6jEz7Ub5NbN5RxNQLxji5kwRKjtIrmxj7LRRcanJTlw= |
| 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), 236 ms totalPASS
https://seriouseats.com
92 ms · HTTP/1.1
https://www.seriouseats.com/
144 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://seriouseats.com | 301 | 92 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.seriouseats.com/ | 200 | 144 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 1 URLsPASS
User-agent: *
Disallow: *.pdf
Disallow: /embed?
User-agent: Pinterest
Disallow:
User-agent: Pinterestbot
Disallow:
User-agent: CCBot
Disallow: /
User-agent: ChatGPT-User
Disallow: /thmb/
User-agent: OAI-SearchBot
Disallow: /thmb/
User-agent: GPTBot
Disallow: /thmb/
User-agent: news-please
Disallow: /
User-agent: anthropic-ai
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: Claude-Web
Disallow: /
User-agent: cohere-ai
Disallow: /
User-agent: ImagesiftBot
Disallow: /
User-agent: FriendlyCrawler
Disallow: /
User-agent: Quora-Bot
Disallow: /
User-agent: omgilibot
Disallow: /
User-agent: omgili
Disallow: /
User-agent: PerplexityBot
Disallow: /
User-agent: Perplexity-User
Disallow: /
User-agent: Google-Extended
Disallow: /
Sitemap: https://www.seriouseats.com/sitemap.xml
Sitemap: https://www.seriouseats.com/google-news-sitemap.xml
A+Domain Intelligenceseriouseats.com — via MarkMonitor Inc., 20 years, 3 months old, hosted on CloudflarePASS
262 days
April 7, 2027
81 days
Issued by Let's Encrypt
20 years, 3 months
Registered April 7, 2006
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS13335
172.66.1.220
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