Security 10 min read ·
Chrome Now Warns Before Opening HTTP Sites: How to Fix Yours
Chrome now shows a warning before opening any website that is not secure (HTTP). See why your site triggers it and fix it with free SSL and a redirect.
Chrome now asks before it opens a public website over plain HTTP. Instead of the small "Not secure" label in the address bar, visitors get a full-page warning that says "yourdomain.in doesn't support a secure connection with HTTPS", with buttons to go back or continue. To get rid of it, your site needs a working SSL certificate on both the bare domain and the www address, and every http:// address has to redirect to https://. A free Let's Encrypt certificate is all you need.
The short version, as of 15 November 2026:
- The warning has been on by default since Chrome 154 (stable on 22 September 2026), and Google said on 21 October 2026 that it now covers all users.
- It appears when Chrome can't load your site over HTTPS. Usually there's no certificate, the certificate covers only one of
yourdomain.inandwww.yourdomain.in, or a redirect passes through an HTTP-only address. - The fix: get a certificate for both names, send everything to one HTTPS address with a single 301 redirect, then clean up old
http://links inside your site.
What the Chrome warning says, and who sees it
The warning comes from Chrome's Always use secure connections setting. Google announced in its October 2025 post HTTPS by default that it would switch the setting on for everyone. The Chrome 154 release notes list "Ask before HTTP on by default": Chrome "prompts users by default when they connect to a site over an insecure (http) connection." On 21 October 2026 the Chrome security team wrote that Chrome now warns before insecure HTTP connections for all users by default.
This is the wording in Chromium's source code for the default warning, as of 15 November 2026:
- The heading reads "yourdomain.in doesn't support a secure connection with HTTPS", and the browser tab says "Site is not secure".
- The text warns that attackers can see and change information sent to or from the site, says it's safest to visit later if you're on a public network, and suggests the visitor contact the site owner and ask them to upgrade to HTTPS.
- The two buttons are "Go back" and "Continue to site".
A customer can still reach your site with one extra click, but plenty won't, especially on an enquiry or payment page. The warning also tells them, in Chrome's own words, that the problem is yours to fix. How it behaves:
- Chrome asks the first time someone visits an HTTP site. After they click through, Google says Chrome won't warn again unless they go at least two weeks without visiting. Chromium's developer guide puts it at 15 days, renewed on every visit.
- By default there's no warning for addresses that can't get a public certificate, such as
192.168.0.1or a single-word intranet name. - Users can turn the setting off, but you can't expect customers to do that for you.
- Google's early figures: nearly 95% of Chrome users on desktop see no HTTP warning in a given week, fewer than 1% see three or more, and the rate on mobile is lower still. Most sites already use HTTPS, so an HTTP site stands out.
When did Chrome start warning before opening HTTP sites?
Chrome rolled the change out in steps. Dates are from Google's posts and Chrome's release notes:
| When | What happened |
|---|---|
| Chrome 141 (2025) | Google tested the setting switched on by default for public sites with a small share of users. |
| 28 October 2025 | Google announced the plan: Enhanced Safe Browsing users first in Chrome 147 (April 2026), then everyone with Chrome 154 (October 2026). |
| Earlier in 2026 | The warning went live for people using Safe Browsing's Enhanced Protection mode, as Google's October 2026 post confirms. |
| 22 September 2026 | Chrome 154 reached the stable channel with "Ask before HTTP on by default". |
| 21 October 2026 | Google confirmed the warning is on by default for all users and published its first warning-rate figures. |
Why does my website say "doesn't support a secure connection"?
Chrome now tries HTTPS first, even when someone clicks an http:// link. According to Chromium's Ask-before-HTTP adoption guide for site owners, the warning appears when Chrome can't connect over HTTPS but might be able to over HTTP. For small business sites, the usual causes are:
- No certificate at all. This is common on older sites, on hosting without free SSL, and on sites that moved hosts without setting up a new certificate.
- The certificate covers one name but not the other. If it covers
www.yourdomain.inbut notyourdomain.in, everyone who types the bare domain gets the warning. - An HTTP-only step in a redirect. Chromium's own example:
http://example.comredirects tohttp://www.example.com, but the bare domain has no HTTPS, so visitors are warned even though the final page is secure. Every hop counts, and several insecure hops can mean several warnings. - Domain forwarding. If your domain simply forwards to another page, such as an old blog or a social profile, the forwarding service has to support HTTPS too. Chromium's guide suggests asking the forwarding provider.
Old http:// links on visiting cards, QR codes or your Google Business Profile aren't a problem in themselves. Chrome upgrades them to HTTPS, so they work as long as HTTPS works on that exact name.
An expired or mismatched certificate is a separate problem. An https:// address with a broken certificate shows Chrome's existing "Your connection is not private" error, and Chromium says those errors are not changing.
How to check your site in two minutes
- Open a Chrome Guest window, so an earlier "Continue to site" click doesn't hide the warning. Type
http://yourdomain.in, thenhttp://www.yourdomain.in. Both should end up onhttps://with no warning. - Check the redirect from a terminal.
curlis built into Windows 10 and 11, macOS and Linux:
You want acurl -I http://yourdomain.in curl -I http://www.yourdomain.in301status and aLocation:line that starts withhttps://, such as:HTTP/1.1 301 Moved Permanently Location: https://yourdomain.in/ - For the full redirect chain, open DevTools (F12), go to the Network tab, tick Preserve log and load the
http://address. After the first request, every step should behttps://. Chromium's guide recommends this test.
| What you see | Likely cause | Fix |
|---|---|---|
The http:// page loads with no redirect, and Chrome warns | No certificate | Get a free certificate, then add the redirect |
| One name works, the other warns | The certificate covers only one name, or DNS for that name points elsewhere | Point both names at the server and reissue the certificate for both |
http://yourdomain.in goes to http://www... first | An insecure hop in the redirect chain | Redirect straight to the final https:// address in one step |
ERR_TOO_MANY_REDIRECTS | Two redirects fighting, such as a plugin and the server, or a proxy that talks to your server over HTTP | Keep one redirect rule |
| "Your connection is not private" | The certificate has expired or doesn't match the name | Renew or reissue it |
How to get a free SSL certificate in India
You don't need to buy one. Let's Encrypt is a free, automated certificate authority run by the non-profit Internet Security Research Group, and every major browser trusts its certificates. A certificate can only be issued once your domain points at the server, and it must cover both yourdomain.in and www.yourdomain.in.
- Shared hosting: look for SSL or Let's Encrypt in your control panel. Our guide to connecting a domain to hosting shows the DNS records for the bare domain and for www.
- A VPS: install Certbot and request one certificate for both names. The full steps are in what an SSL certificate is:
sudo certbot --nginx -d yourdomain.in -d www.yourdomain.in - Website builders and store platforms normally issue the certificate themselves once you connect your domain. Check their domain settings for an SSL or HTTPS status.
The maximum lifetime of a certificate is being cut in stages, so renewal has to happen automatically. Our post on SSL certificate validity in 2026 has the dates.
How to redirect HTTP to HTTPS with .htaccess or nginx
Pick one address, either the bare domain or www, and send every other version there with a single permanent (301) redirect. Get the certificate first: redirecting to HTTPS without one just moves the error.
Apache or LiteSpeed (.htaccess)
Many shared hosts use Apache or LiteSpeed. Add this at the top of the .htaccess file in your site's root folder, above the # BEGIN WordPress block if there is one. It sends http:// and www to https://yourdomain.in in one hop:
RewriteEngine On
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} ^www\. [NC]
RewriteRule ^ https://yourdomain.in%{REQUEST_URI} [L,R=301]
If you'd rather use www as the main address, use these three lines instead:
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteRule ^ https://www.yourdomain.in%{REQUEST_URI} [L,R=301]
Browsers remember 301 redirects for a long time, so test with R=302 first and change it to R=301 once it works. If a CDN or proxy sits in front of your site, it may reach your server over plain HTTP, which makes this rule loop. In that case, use the CDN's own "always use HTTPS" setting instead. On HostEthical web hosting you don't need this: once your certificate is issued, the server already redirects http:// to https://. It runs nginx, which ignores .htaccess files, so a rule like this has no effect there anyway.
nginx (VPS)
Add these two server blocks, and leave your existing HTTPS block for yourdomain.in as it is. The first catches all plain HTTP. The second sends https://www to the bare domain:
server {
listen 80;
listen [::]:80;
server_name yourdomain.in www.yourdomain.in;
return 301 https://yourdomain.in$request_uri;
}
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name www.yourdomain.in;
ssl_certificate /etc/letsencrypt/live/yourdomain.in/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/yourdomain.in/privkey.pem;
return 301 https://yourdomain.in$request_uri;
}
sudo nginx -t && sudo systemctl reload nginx
If Certbot has already added its own redirect lines (marked "managed by Certbot"), keep either those or yours, not both.
Lock it in with HSTS
Chromium's guide says HSTS "takes precedence" over Chrome's automatic upgrades and the HTTP warning: a browser that has seen the header never tries plain HTTP on your domain again. Add it only once HTTPS works everywhere, and start with a short lifetime:
# Apache / LiteSpeed (.htaccess)
Header always set Strict-Transport-Security "max-age=300"
# nginx (inside the HTTPS server block)
add_header Strict-Transport-Security "max-age=300" always;
After a week or two with no problems, raise it to max-age=31536000 (one year). Leave out includeSubDomains unless every subdomain, including ones such as mail. or shop., has HTTPS.
How to fix mixed content and switch WordPress to HTTPS
Mixed content means an HTTPS page loads images, scripts or stylesheets over http://. According to web.dev's guide to mixed content, browsers block insecure scripts, stylesheets and iframes, which can break menus, sliders and forms. Chrome tries to load insecure images, audio and video over HTTPS and drops them if no secure copy exists. To find the culprits, open DevTools and check the Issues tab.
On WordPress, take a backup first, then:
- Go to Settings, General and make sure the WordPress Address (URL) and Site Address (URL) both start with
https://, with no slash at the end. If the fields are greyed out, they are set inwp-config.phpasWP_HOMEandWP_SITEURL, so change them there. - Replace old
http://links stored in your posts and settings. With WP-CLI, do a dry run first, then the real run:
Repeat forwp option get home wp search-replace 'http://yourdomain.in' 'https://yourdomain.in' --skip-columns=guid --dry-run wp search-replace 'http://yourdomain.in' 'https://yourdomain.in' --skip-columns=guidhttp://www.yourdomain.inif your old links used www. WordPress's migration guide says never to change the GUID column, which is why--skip-columns=guidis there. Without WP-CLI, a search-and-replace plugin does the same job. - Check the places a search-replace can miss: the theme's logo setting, page-builder backgrounds, header and footer scripts, and old map or video embeds.
- Clear your caching plugin and any CDN cache, then reload the page with the Issues tab open.
Outside your site, change the website link on your Google Business Profile, social media bios, WhatsApp Business profile and email signature to https://. Use https:// on anything you print from now on. If you use Google Search Console, a Domain property covers both versions of the site.
Frequently asked questions
Why does Chrome say a site doesn't support a secure connection?
Since Chrome 154 in September 2026, Chrome tries HTTPS first and asks before loading a public site over plain HTTP. The full-page warning appears when the site has no working HTTPS on the address you opened. The usual reasons are no SSL certificate, a certificate that covers only the www or only the bare domain, or a redirect that passes through an HTTP-only address. Only the site owner can fix it.
How do I make my website HTTPS for free?
Use a free Let's Encrypt certificate. Most web hosts issue one from the control panel or automatically once your domain points to their server. On a VPS, install Certbot and request one certificate covering both yourdomain.in and www.yourdomain.in. Then add a permanent 301 redirect from http:// to https://, and change your site's own links, such as the WordPress Address and Site Address settings, to https://.
Can visitors still open my website if Chrome shows this warning?
Yes. The warning has a Continue to site button, and after someone clicks it Chrome won't warn them again unless they stay away from the site for about two weeks. Many visitors will click Go back instead, though, especially before filling in a form or paying. Visitors can also switch off the Always use secure connections setting, but you can't rely on customers doing that.
How do I redirect HTTP to HTTPS?
On Apache or LiteSpeed hosting, add a rewrite rule at the top of the .htaccess file in your site's root folder that sends every request with HTTPS off to https:// with a 301 status. On nginx, add a server block listening on port 80 that returns 301 to the https:// address. Redirect straight to the final address in one step, and get the certificate before you add the redirect.
Does HTTPS fix the Not secure label in Chrome?
Yes, if every part of the page loads over HTTPS. Once the site has a valid certificate and redirects HTTP to HTTPS, both the full-page warning and the Not secure label go away. If the page still loads images, scripts or stylesheets from http:// addresses, Chrome blocks or upgrades them, and the page can break. Find them in the Issues tab of Chrome DevTools and change those links to https://.