Skip to content
https://www.whoop.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
307 Temporary Redirect
Checks
9
6 PASS 3 REVIEW
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
TLS Certificate Expiry & Recommendations
75 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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
B
CDN & Delivery
Vercel
REVIEW
Vercel
Info::
Site is served via Vercel CDN
Got: x-vercel-id: cdg1::zrfsx-1775593250946-647d5cb749ab
CDN Detected: Vercel
Provider Vercel Evidence x-vercel-id: cdg1::zrfsx-1775593250946-647d5cb749ab
A
DNS Records
2 A records, 2 ms lookup
PASS
2 A records, 2 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 76.76.21.241, 66.33.60.193
Info::
No IPv6 (AAAA) records
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: cname.vercel-dns.com
Info::
4 nameserver(s) configured
Got: ns3.vercel-dns-3.com, ns4.vercel-dns-3.com, ns2.vercel-dns-3.com, ns1.vercel-dns-3.com
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: 2 ms
Got: 2 ms
A76.76.21.241, 66.33.60.193
AAAA—
CNAMEcname.vercel-dns.com
NSns3.vercel-dns-3.com, ns4.vercel-dns-3.com, ns2.vercel-dns-3.com, ns1.vercel-dns-3.com
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 2 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)

A
Redirect Chain
1 redirect(s), 914 ms total
PASS
1 redirect(s), 914 ms total
Info::
Single redirect
Got: https://www.whoop.com → https://www.whoop.com/fr/en/ (307)
Info::
Redirect overhead: 914 ms total
Got: 914 ms

https://www.whoop.com

90 ms · HTTP/1.1

307

https://www.whoop.com/fr/en/

824 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.whoop.com30790 msHTTP/1.1Vercel
2https://www.whoop.com/fr/en/200824 msHTTP/1.1Vercel

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 223 URLs
PASS
robots.txt present, sitemap with 223 URLs
Info::
robots.txt is present
Got: 67 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 223 entries
Info::
Sitemap index with 223 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 67 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /

Sitemap: https://www.whoop.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 223 entries Valid XML Yes
Child Sitemaps:
A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.whoop.com/
308https://whoop.com/

HTTP → HTTPS

308http://www.whoop.com/ → https://www.whoop.com/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
whoop.com — via GoDaddy.com, LLC, 29 years, 11 months old, hosted on AWS
PASS
whoop.com — via GoDaddy.com, LLC, 29 years, 11 months old, hosted on AWS
Info::
Domain registered until Sep 16, 2027 (1 years, 5 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: GoDaddy.com, LLC
Info::
Hosting: AWS
Got: AS16509
Domain expiry

457 days

September 16, 2027

SSL certificate

75 days

Issued by Let's Encrypt

Domain age

29 years, 11 months

Registered September 17, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

76.76.21.21

Registrar

GoDaddy.com, LLC

Lock status unknown 4 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
Registrar GoDaddy.com, LLC
Created September 17, 1996 (29 years, 11 months ago)
Expires September 16, 2027 (1 years, 5 months)
Last Updated September 17, 2022
Name Servers ns-1478.awsdns-56.org, ns-1687.awsdns-18.co.uk, ns-75.awsdns-09.com, ns-851.awsdns-42.net
DNSSEC Not enabled
Hosting
IP Address 76.76.21.21
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.1s)

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

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

Connection waterfall

DNS Lookup 40 ms TCP Connect 1 ms TLS Handshake 36 ms Server Processing 54 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