The Chrome 154 HTTP warning is now live: since the stable release on September 22, 2026, Chrome asks for your permission before it opens an unencrypted public website. If you only visit HTTPS sites, you’ll probably never see it. If you still open old HTTP pages, expect a quick “are you sure?” screen.
Here are the facts you can scan in ten seconds.
- Chrome 154 reached the stable channel on September 22, 2026, according to the official Chrome 154 release notes.
- The prompt appears when you open a public site over plain
http. - Local addresses, single-word hostnames, and intranet shortcuts are left alone.
- Chrome only warns on new or rarely visited insecure sites, not every single time.
- You can change the behavior in Chrome’s security settings.
Short version: it’s a small speed bump aimed at the few sites that never moved to HTTPS.
What the Chrome 154 HTTP warning actually does
Chrome now tries HTTPS first. If a public site doesn’t support it, you get a confirmation screen before the page loads. You can continue, but you have to choose to.
This is the “Always Use Secure Connections” setting, which Google has been testing for a while. It started with Enhanced Safe Browsing users in Chrome 147 in April 2026, then became the default for everyone in Chrome 154, as laid out on the Google Security Blog.
Why bother? One unencrypted connection is enough for someone on the same Wi-Fi to read or change what you see. Google’s own line is that even a few percent of insecure traffic is a lot of page loads.
How often will you really see it?
Rarely. Google’s early tests found fewer than 3% of page loads triggered a warning. The median person saw less than one prompt a week, and even heavy cases stayed under three a week.
Chrome also suppresses repeats. If you keep visiting the same HTTP page, it stops nagging you about it, so the warning mostly shows up on first visits and sites you rarely open.
That matters if you use older forums, small business sites, or archived pages. They may be the ones that still serve plain HTTP.
What’s exempt and what isn’t
The warning is built for the open internet, not your home network. This table shows where it applies.
| Type of address | Example | Warning? |
|---|---|---|
| Public website over HTTP | http://old-site.example | Yes, on first or rare visits |
| Local router page | 192.168.0.1 | No |
| Single-word hostname | http://intranet | No |
| Site that supports HTTPS | https://appauxin.com | No |
This split keeps the warning from annoying developers and office workers who rely on internal tools that never had HTTPS certificates.
Don’t ignore the 108 security fixes
The HTTP prompt gets the headlines, but Chrome 154 also patches 108 vulnerabilities. According to Lynxflow, several are rated Critical and touch components like ANGLE, GPU, WebGL, Service Worker, and Full-screen.
Chrome usually updates itself in the background, but it only applies the update after a restart. Open the three-dot menu, go to Help, then About Google Chrome, and let it check.
If you care about browser safety in general, our look at the Edge Manifest V2 shutdown shows another browser change that could affect your extensions this year.
What site owners should check this week
If your site still loads over HTTP, visitors on Chrome 154 can hit a warning page before they see a single word. That’s a quick way to lose readers and sales.
Most hosts offer free certificates, so the fix is usually a few clicks. Once the certificate is on, redirect every HTTP address to its HTTPS version and test your key pages.
Also look for old images, scripts, or embeds that still load over HTTP. Those “mixed content” leftovers can trigger browser complaints even after you switch.
How to change the setting
You can adjust it in the Security section of Chrome’s settings. The option is called “Always Use Secure Connections,” and it lets you limit the check to public sites or extend it to private networks too.
Most people should leave it on. If a site you trust is stuck on HTTP, you can click through once and Chrome will relax on repeat visits.
For a bigger security upgrade on the Windows side, read how Windows 11 post-quantum encryption works.
Frequently Asked Questions
Does the Chrome 154 HTTP warning block websites?
No. It’s a confirmation screen, and you can still continue to the site if you choose to.
Will it warn me about my router or local network?
No, not by default. Local IP addresses, single-word hostnames, and intranet shortcuts are exempt in the public-sites mode.
How do I update to Chrome 154?
Open the three-dot menu, choose Help, then About Google Chrome. Chrome will download the update and ask you to relaunch.
Can I turn the HTTP warning off?
Yes. Change the “Always Use Secure Connections” setting in Chrome’s security preferences. Turning it off isn’t a great idea on public Wi-Fi, though.
Our take
Leave it on and update Chrome today. The warning will barely touch your day, and the one time it does, it’s probably catching a site that should have switched to HTTPS years ago. If you run a website, check it now, because a scary warning screen costs you visitors fast.
Leave a Reply