Chrome HTTPS Warning Check
Chrome 154 (22 September 2026) turned HTTPS-First on by default. Chrome tries HTTPS first and warns when any hop in the visit is still plain HTTP — even if a later redirect lands on HTTPS. This check shows every hop, scheme, and status code so you can see what Chrome will upgrade.
We reuse the same redirect-chain report as the rest of the site. No extra probe, no change to grading. The result line says whether Chrome would warn: only when a hostname reached over http:// does not serve valid HTTPS.
Enter any domain — no signup, results in seconds.
What Chrome 154 changed
A final HTTPS page is not enough
A chain like http://example.com → http://www.example.com → https://www.example.com still exposes the first two hosts as HTTP. Chrome upgrades each of those steps on its own and warns if HTTPS is missing or the certificate does not cover that name.
How to fix it
Put a 301 from HTTP to HTTPS on every hostname that still answers on port 80 — apex, www, and any old hosts in the chain — and give each of those names a valid certificate. Step-by-step for Nginx, Apache, Cloudflare, and WordPress: How to fix HTTP to HTTPS redirect.
Related tools: