Google announced on 28 October 2025 that Chrome will ask users for permission before visiting any public site served over plain HTTP. The change arrives with Chrome 154 in October 2026. It is already live for people using Enhanced Safe Browsing in Chrome 147.
What is going on
HTTP is the older way a browser and a website talk to each other. The traffic is not encrypted, so anyone between the visitor and the server can read or change it. HTTPS is the same conversation inside a sealed envelope.
Today Chrome marks HTTP pages as "Not secure" in the address bar. From Chrome 154 it goes a step further and asks the visitor to confirm before the page loads. The page still opens, but only after an extra click and a warning.
Who is affected
Any public website that is still reachable over plain HTTP will trigger the warning. That includes cases site owners often forget:
- Subdomains such as
blog.,shop.ormail.that were never moved to HTTPS - Old HTTP links and redirects that pass through an unencrypted step
- Landing pages, staging sites and microsites hosted outside the main platform
Sites that already serve every page over HTTPS with a valid certificate see no change. Private and internal addresses are not the target of this warning.
What to do now
- Install a valid certificate for your domain and every subdomain you publish. Most hosting panels offer this at no extra cost.
- Redirect all HTTP traffic to HTTPS at the server or CDN level, so an old link never lands on an unencrypted page.
- Fix mixed content. These are images, scripts or stylesheets on an HTTPS page that are still loaded over HTTP. Update the links to HTTPS.
- Check the whole redirect chain. If a link goes HTTP to HTTP to HTTPS, remove the unencrypted hop.
- Update anything that points at your site, including printed material, email footers, ad campaigns and partner links.
You have until October 2026, which is enough time to plan the work rather than rush it.
How to check your own site
The free Website Security Check looks at your certificate and TLS setup, missing security headers, outdated CMS versions, known-vulnerable plugins and email-authentication gaps, so you can see quickly whether your HTTPS setup holds up. If you want deeper coverage of your own site, the Full scan adds active OWASP Top 10 testing, port and service checks with CVE matching, WordPress and Magento deep scans and exposed-file checks. It runs only against sites whose ownership you have verified, and you can run a full scan once that is done.
Source: Google Security Blog, October 2025.
Comments
No comments yet.