Skip to content
https://www.redis.io

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
B
DNS Records
2 A records, 31 ms lookup
REVIEW
2 A records, 31 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.16.102.104, 104.16.101.104
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6810:6668, 2606:4700::6810:6568
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: www.redis.io.cdn.cloudflare.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 31 ms
Got: 31 ms
A104.16.102.104, 104.16.101.104
AAAA2606:4700::6810:6668, 2606:4700::6810:6568
CNAMEwww.redis.io.cdn.cloudflare.net
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 31 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

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.

Why this matters

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'.

Why this matters

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)

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.redis.io/
200https://redis.io/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://www.redis.io/ https://www.redis.io/

Consistent

B
TLS Certificate Expiry & Recommendations
62 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

62
days left
0d 30d 60d 90d+

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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9e8bcee75961998a-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9e8bcee75961998a-CDG
A
Redirect Chain
1 redirect(s), 232 ms total
PASS
1 redirect(s), 232 ms total
Info::
Single redirect
Got: https://www.redis.io → https://redis.io/ (301)
Info::
WWW normalization redirect

https://www.redis.io

67 ms · HTTP/1.1

301

https://redis.io/

164 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.redis.io30167 msHTTP/1.1cloudflare
2https://redis.io/200164 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6810:6668, 2606:4700::6810:6568
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700::6810:6668, 2606:4700::6810:6568 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 14 URLs
PASS
robots.txt present, sitemap with 14 URLs
Info::
robots.txt is present
Got: 372 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 14 entries
Info::
Sitemap index with 14 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 372 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# 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

A
Domain Intelligence
redis.io — via Name.com, Inc., 16 years, 1 months old, hosted on Cloudflare
PASS
redis.io — via Name.com, Inc., 16 years, 1 months old, hosted on Cloudflare
Warning::
Domain expires in 51 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires May 28, 2026
Info::
Registrar: Name.com, Inc.
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

EXPIRED

May 28, 2026

SSL certificate

62 days

Issued by Google Trust Services

Domain age

16 years, 1 months

Registered May 28, 2010

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.18.25.196

Registrar

Name.com, Inc.

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
Registrar Name.com, Inc.
Created May 28, 2010 (16 years, 1 months ago)
Expires May 28, 2026 (1 months)
Last Updated May 9, 2025
Name Servers ns-247.awsdns-30.com, ns-1248.awsdns-28.org, ns-791.awsdns-34.net, ns-1731.awsdns-24.co.uk
Registrant Domain Protection Services, Inc.
Hosting
IP Address 104.18.25.196
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: whois (1.4s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

A+
HTTP Probe Timing
Total 103 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
41 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
103 ms
Total Time Total request time from DNS lookup through full response.
103 ms

Connection waterfall

DNS Lookup 41 ms TCP Connect 16 ms TLS Handshake 22 ms Server Processing 24 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback