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)
DTLS Certificate Expiry & RecommendationsAction13 days until leaf cert expires — 5 issues to addressFIX
Certificate validity
Recommended actions
- Renew certificate — 13 days remaining
- 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
BDNS Records4 A records, 13 ms lookupREVIEW
| A | 151.101.129.57, 151.101.193.57, 151.101.1.57, 151.101.65.57 |
| AAAA | 2a04:4e42::313, 2a04:4e42:200::313, 2a04:4e42:400::313, 2a04:4e42:600::313 |
| CNAME | prod.www-fastly-com.map.fastly.net |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.
Learn more ▾ ▴
RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.
Source: RFC 1034
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.
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
A+Redirect ChainNo redirects — direct accessPASS
https://www.fastly.com
18 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.fastly.com | 200 | 18 ms | HTTP/1.1 | Artisanal bits |
A+Crawlabilityrobots.txt present, sitemap with 5 URLsPASS
User-agent: *
Disallow: /ja/*
Disallow: /labs/*
Disallow: /production-2019/*
Disallow: /cassets/*
Disallow: /resources?*
Disallow: /altitude/2020
Disallow: /astro-header/*
Disallow: /*/astro-header/*
Disallow: /feature-o11y/*
Disallow: /*/feature-o11y/*
Disallow: /learning/fastly-research-methodology-glossary
Sitemap: https://www.fastly.com/sitemap/sitemap-index.xml
Host: https://www.fastly.com
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligencefastly.com — via MarkMonitor Inc., 24 years, 1 months old, hosted on FastlyPASS
325 days
July 8, 2027
13 days
Issued by Certainly
24 years, 1 months
Registered July 8, 2002
Not enabled
Protects against DNS spoofing
Fastly
ASN AS54113
151.101.1.57
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Renew the TLS certificate or verify auto-renewal is working
- Enable DNSSEC to protect visitors from DNS spoofing
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