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)
BDomain Intelligencenetlify.app — via Name.com, Inc., 8 years old, hosted on AWSREVIEW
EXPIRED
May 8, 2026
332 days
Issued by DigiCert Inc
8 years
Registered May 8, 2018
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
52.52.192.191
Name.com, Inc.
Expiry timeline
Recommended actions
- Domain has EXPIRED — renew immediately to avoid total site outage
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
This domain expires on May 8, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.
Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.
Source: ICANN renewal policy
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
BTLS Certificate Expiry & Recommendations332 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- 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 & DeliveryNetlifyREVIEW
A+DNS Records2 A records, 10 ms lookupPASS
| A | 52.52.192.191, 13.52.188.95 |
| AAAA | 2600:1f1c:446:4900::258, 2600:1f1c:446:4900::259 |
| CNAME | — |
| NS | dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net |
| MX | — |
| TXT | google-site-verification=0KCpoJchrixypEMvtkzLtj6VMqMXKcuWS7j2jjjDcys SPF v=spf1 -all _kvz3va36b5cudpl46gbej22cfyyw908 |
| 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), 47 ms totalPASS
https://netlify.app
22 ms · HTTP/1.1
https://www.netlify.com/
24 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://netlify.app | 301 | 22 ms | HTTP/1.1 | Netlify |
| 2 | https://www.netlify.com/ | 200 | 24 ms | HTTP/1.1 | Netlify |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 49 URLsPASS
User-agent: *
Allow: /
Sitemap: https://www.netlify.com/sitemap.xml
Sitemap: https://www.netlify.com/guide-to-composable-architecture/sitemap.xml
- https://www.netlify.com/guide-to-composable-architecture/backend-databases-headless-cms/
- https://www.netlify.com/guide-to-composable-architecture/business-case-for-composable/
- https://www.netlify.com/guide-to-composable-architecture/ci-cd-building-deploying-hosting/
- https://www.netlify.com/guide-to-composable-architecture/common-enterprise-challenges/
- https://www.netlify.com/guide-to-composable-architecture/common-website-features-tooling/
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent