Skip to content
https://rei.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
9
4 PASS 4 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 403 Expected: 301 redirect to HTTPS

www / non-www

403https://www.rei.com/
200https://rei.com/

HTTP → HTTPS

403http://rei.com/

HTTP version does not redirect to HTTPS

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

Certificate validity

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

Recommended actions

  • 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
A+
DNS Records
1 A records, 79 ms lookup
PASS
1 A records, 79 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.214.208.32
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: ns17.ultradns2.org, ns17.ultradns2.com, edns3.ultradns.org, edns3.ultradns.com, edns3.ultradns.net, edns3.ultradns.biz
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 79 ms
Got: 79 ms
A23.214.208.32
AAAA
CNAME
NSns17.ultradns2.org, ns17.ultradns2.com, edns3.ultradns.org, edns3.ultradns.com, edns3.ultradns.net, edns3.ultradns.biz
MX
10 mxa-0003ca03.gslb.pphosted.com
10 mxb-0003ca03.gslb.pphosted.com
TXT
MS=ms30598333
0438BBB77053C87F4B091EEDC222D6C2C5EE0E76
onetrust-domain-verification=ca95e58bbf1f4d2ba04beae563ff188a
google-site-verification=jVRhO_fihTy4kc7Oz3TGmd-1JmoUZCmpC70XJOiZgdg
google-site-verification=lZ1GF4wl3TFvxaItqytAtkRydtqj-tbT25JgRRraBG8
onx=4e0145c4-5e57-4987-8637-2af43790b760
atlassian-domain-verification=w92kXgtqmYeFMRj3nXJyq5m90ffZZsoe79dKODeOjj4PHxDk71...
google-site-verification=BePzQJxbdbxrLnT2UWKO-L0yM8i_-x4kJ2wqV6uqTQU
flexera-domain-verification-yjsrpksnrtbqtknr
_92akarc2f5jz896ef43uhdokds3smvd
apple-domain-verification=9l3yvEMMyPiozeuxMPU14nMxYN5Or7-xJyev3iw7sl0
amazonses:KsIm8aktFeQizdQYGVrPjl14gXU3JPzhFze3qbNp/Xg=
wiz-domain-verification=7ffeb2c0f895022213c1cc06b73e41e8b1b625877927ff4ee0069ca3...
adobe-idp-site-verification=26d872c3-686e-4ce5-9022-188c7705cd74
apple-domain-verification=xlpiO8xLLztRGlkCVTsPvNhOkBSF775yxO2wNvMct1Y
mongodb-site-verification=wSFZ8lMnVINIDzTWEYPExi2Dpo9TZfgN
google-site-verification=VO7Ay2sQaZ5OoH3sgZYYq77ZfhvcLHvWH_M4v3f1y5I
slack-domain-verification=DaSbgScODYOXtAhPHLtX7q4Z7xJ5xwManApSFof0
jamf-site-verification=B5_eWfThkW16GMdQmOD4mg
SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ip4:204.89.17.163 ip4:204.89...
+gAr5qQyMwWTvpVf1KM9mhYEbIQdfi+E0uGOJPVHCKy2GiBtZAa9bkpUBef3ueOh4RID9GWY0+bFMqLq...
smartsheet-site-validation=2a6ReakV7XD3dkbbbUnVOb6TdkvHq0aE
onx=a680793d-4b53-4f4f-b7d0-18d115d85a41
_osm5o4dmuk9i5ephxepy8b7t52iuav0
h1-domain-verification=4zyQXkN657uQPPMH1kFjj7P6SGeLMbVq8eyKkqtZCCPHs1BX
CAALookup not available with standard resolver
Resolved in 79 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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.

A+
Redirect Chain
0 redirect(s), 95 ms total
PASS
0 redirect(s), 95 ms total

https://rei.com

95 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://rei.com40395 msHTTP/1.1
A+
Domain Intelligence
rei.com — via CSC Corporate Domains, Inc., 30 years, 6 months old, hosted on Akamai
PASS
rei.com — via CSC Corporate Domains, Inc., 30 years, 6 months old, hosted on Akamai
Info::
Domain registered until Mar 14, 2027 (10 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: CSC Corporate Domains, Inc.
Warning::
Registrar lock is NOT enabled
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.
Info::
Hosting: Akamai
Got: AS16625
Domain expiry

209 days

March 14, 2027

SSL certificate

114 days

Issued by DigiCert Inc

Domain age

30 years, 6 months

Registered March 13, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS16625

23.214.208.32

Registrar

CSC Corporate Domains, Inc.

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created March 13, 1996 (30 years, 6 months ago)
Expires March 14, 2027 (10 months)
Last Updated March 10, 2026
Name Servers edns3.ultradns.biz, edns3.ultradns.com, edns3.ultradns.net, edns3.ultradns.org, ns17.ultradns2.com, ns17.ultradns2.org
DNSSEC Not enabled
Hosting
IP Address 23.214.208.32
ASN AS16625 (AKAMAI-AS - Akamai Technologies, Inc., US)
Provider Akamai
Data source: rdap (0.4s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

Why this matters

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

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

Connection waterfall

DNS Lookup 30 ms TCP Connect 25 ms TLS Handshake 28 ms Server Processing 40 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