Website readiness profile · Snapshot 23 October 2026
change.org
change.org's public homepage, certificate and DNS checked against 31 practices and compared with 343 Uncategorized sites.
- Readiness index
- 82/100
- Ahead of
- 95%
- Practices observed
- 23/31
- Popularity band
- Top 5K
Uncategorized median 62
of measured Uncategorized sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: change.org. Thin bar: Uncategorized peer median.
Enable
95/100
Peers 80
Harden
72/100
Peers 54
Accelerate
90/100
Peers 58
Recover
0/100
Peers 12
Priority fixes for change.org
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HSTS kept for at least a year
Observed: Strict-Transport-Security was sent with a max-age of 180 days, below the one-year benchmark.
Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.
What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.
On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.
34% of Uncategorized peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Harden
Certificate lifetime of 100 days or less
Observed: The certificate from Amazon had a 197-day validity period, longer than the 100-day maximum that applies from March 2027.
What to do: Move to automated issuance and renewal now, while you still have time to test it.
67% of Uncategorized peers do this.
Priority 3 · Accelerate
HTTP/3 advertised
Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.
What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
On Amazon CloudFront: Select HTTP/3 in the distribution's supported HTTP versions.
33% of Uncategorized peers do this.
Priority 4 · Harden
X-Content-Type-Options: nosniff
Observed: The homepage response did not include X-Content-Type-Options: nosniff.
What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.
On Amazon CloudFront: Enable it in a response headers policy (security headers section).
44% of Uncategorized peers do this.
What change.org already does well
Practices fewer than half of Uncategorized peers use.
- security.txt publishedsecurity.txt with a contact found.4.5% of peers
- CAA records limit who can issue certificatesCAA limits issuance to amazonaws.com, comodoca.com, letsencrypt.org and others.8.7% of peers
- Content Security Policy presentContent-Security-Policy present.24% of peers
What we saw
- Homepage checked
- https://www.change.org/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-03-26
- CDN or edge
- Amazon CloudFront
- DNS operators
- Amazon Route 53
- HSTS
- max-age 180 days, includeSubDomains
- DMARC policy
- p=reject
- Homepage HTML
- 301 KB, gzip
- Images on homepage
- 22 (jpg 13, png 5, webp 4)
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
Not observed 8
Observed 23
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- CAA records limit who can issue certificates
- security.txt published
- DMARC policy enforces quarantine or reject
- Framing restricted
- Content Security Policy present
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- 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
Own change.org?
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: change.org. This profile covers configuration only.