Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations49 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
ADNS Records2 A records, 15 ms lookupPASS
| A | 172.64.150.238, 104.18.37.18 |
| AAAA | 2a06:98c1:3101::6812:2512, 2606:4700:4403::ac40:96ee |
| CNAME | — |
| NS | — |
| MX | — |
| TXT | — |
| 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.
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)
ARedirect Chain1 redirect(s), 138 ms totalPASS
https://www.auth0.com
48 ms · HTTP/1.1
https://auth0.com/
90 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.auth0.com | 301 | 48 ms | HTTP/1.1 | cloudflare |
| 2 | https://auth0.com/ | 200 | 90 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (2 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 10 URLsPASS
User-agent: *
Allow: /
Sitemap: https://auth0.com/sitemap.xml
Disallow: /docs/addons/*
Disallow: /terms*
Disallow: /docs/email-wall/*
Disallow: /docs/video-series/*
Disallow: /*wp-includes*
Disallow: /login/*
Disallow: /connect/*
Disallow: /docs*?*utm_source=*
Disallow: /learn/lp-auth0-vs-stormpath*
Disallow: /legal*
- https://auth0.com/sitemap-root.xml
- https://auth0.com/jp/sitemap-root.xml
- https://auth0.com/de/sitemap-root.xml
- https://auth0.com/fr/sitemap-root.xml
- https://auth0.com/es/sitemap-root.xml
- https://auth0.com/pt/sitemap-root.xml
- https://auth0.com/blog/sitemap.xml
- https://auth0.com/docs/sitemap.xml
- https://auth0.com/docs/v2/sitemap.xml
- https://auth0.com/developers/hub/sitemap...
A+Domain Intelligenceauth0.com — via MarkMonitor Inc., 13 years, 7 months oldPASS
463 days
October 18, 2027
49 days
Issued by Let's Encrypt
13 years, 7 months
Registered October 18, 2012
Not enabled
Protects against DNS spoofing
Unknown
2a06:98c1:3101::6812:2512
MarkMonitor Inc.
Expiry timeline
Recommended actions
- 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