Website readiness profile · Snapshot 23 October 2026
stripe.com
stripe.com's public homepage, certificate and DNS checked against 31 practices and compared with 157 Online Payment & Wallets sites.
- Readiness index
- 92/100
- Ahead of
- 98%
- Practices observed
- 26/30
- Popularity band
- Top 50K
Online Payment & Wallets median 64
of measured Online Payment & Wallets sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: stripe.com. Thin bar: Online Payment & Wallets peer median.
Enable
95/100
Peers 72
Harden
95/100
Peers 63
Accelerate
88/100
Peers 61
Recover
0/100
Peers 6
Priority fixes for stripe.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTTP/3 advertised
Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.
Why it matters: HTTP/3 runs over QUIC, which copes better with lossy mobile networks and recovers faster when a connection changes.
What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
35% of Online Payment & Wallets peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Harden
DNSSEC signed
Observed: No DS record was found for stripe.com at its parent zone, so its DNS answers are not DNSSEC-signed.
What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.
On Amazon Route 53: Enable DNSSEC signing for the hosted zone and establish the chain of trust at the registrar.
8.3% of Online Payment & Wallets peers do this.
Guide: Website Uptime Readiness: Prepare Before Traffic Arrives
Priority 3 · Enable
Reachable over IPv6
Observed: No IPv6 (AAAA) address was published for stripe.com.
What to do: Enable IPv6 at your CDN or host and publish the AAAA record it provides.
28% of Online Payment & Wallets peers do this.
Priority 4 · Recover
Nameservers spread across providers
Observed: All nameservers for stripe.com belong to Amazon Route 53.
What to do: Treat this as an advanced step. Add a secondary DNS provider through zone transfers or a multi-provider setup, then test changes carefully, since both providers must stay in sync.
6.4% of Online Payment & Wallets peers do this.
Guide: Website Uptime Readiness: Prepare Before Traffic Arrives
What stripe.com already does well
Practices fewer than half of Online Payment & Wallets peers use.
- security.txt publishedsecurity.txt with a contact found.6.6% of peers
- CAA records limit who can issue certificatesCAA limits issuance to amazon.com, digicert.com, visa.com.18% of peers
- Referrer-Policy setReferrer-Policy present.37% of peers
What we saw
- Homepage checked
- https://stripe.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- DigiCert, 77-day validity, expiring 2026-12-10
- Platform or framework
- Next.js
- DNS operators
- Amazon Route 53
- HSTS
- max-age 730 days, includeSubDomains, preload
- DMARC policy
- p=reject
- Homepage HTML
- 650 KB, gzip
- Images on homepage
- 35 (png 212, jpg 32, webp 7)
Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.
Stack and providers
Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.
All 31 checks
Select a gap for the method and fix. How each check works
Observed 26
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- HTML compressed
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Not measured 1
- Static files cached for 30 days or more
Own stripe.com?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: stripe.com. This profile covers configuration only.