Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNS Records2 A records, 31 ms lookupREVIEW
| A | 104.16.102.104, 104.16.101.104 |
| AAAA | 2606:4700::6810:6668, 2606:4700::6810:6568 |
| CNAME | www.redis.io.cdn.cloudflare.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)
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations62 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- 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
ARedirect Chain1 redirect(s), 232 ms totalPASS
https://www.redis.io
67 ms · HTTP/1.1
https://redis.io/
164 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.redis.io | 301 | 67 ms | HTTP/1.1 | cloudflare |
| 2 | https://redis.io/ | 200 | 164 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 14 URLsPASS
# 20250317
User-agent: *
Disallow: /docs/staging/
Disallow: /wp-admin/
Disallow: */?s=
Disallow: /search/
Disallow: /studio/
Disallow: /maintenance/
Disallow: /thank-you/
Disallow: /preview/
Disallow: /dev/*
Disallow: /404/
Disallow: /404.html
Disallow: /template/*
Disallow: /resources/*.pdf
Allow: /wp-admin/admin-ajax.php
Sitemap: https://redis.io/sitemap_index.xml
- https://redis.io/sitemap/pages.xml
- https://redis.io/sitemap/blog-1.xml
- https://redis.io/sitemap/blog-2.xml
- https://redis.io/sitemap/customers.xml
- https://redis.io/sitemap/resources.xml
- https://redis.io/sitemap/videos.xml
- https://redis.io/sitemap/events.xml
- https://redis.io/sitemap/partners.xml
- https://redis.io/sitemap/press.xml
- https://redis.io/sitemap/glossary.xml
- https://redis.io/sitemap/tutorials.xml
- https://redis.io/sitemap/architecture-di...
- https://redis.io/sitemap/landing-pages.x...
- https://redis.io/docs/latest/sitemap.xml
ADomain Intelligenceredis.io — via Name.com, Inc., 16 years, 1 months old, hosted on CloudflarePASS
EXPIRED
May 28, 2026
62 days
Issued by Google Trust Services
16 years, 1 months
Registered May 28, 2010
Status unknown
Protects against DNS spoofing
Cloudflare
ASN AS13335
104.18.25.196
Name.com, Inc.
Expiry timeline
Recommended actions
- Domain has EXPIRED — renew immediately to avoid total site outage
Consider enabling auto-renewal to prevent accidental expiration.
Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.
Source: ICANN renewal policy