Chrome shows a warning before it even opens a public address that is a site without HTTPS. A padlock on the home page? That is no longer enough. Every other company address needs checking: forgotten subdomains, landing pages from past campaigns, links in email footers and QR codes that still go through http. Below is a short look at the change itself, followed by a checklist to work through in your own organisation.
Table of contents
What is changing in Chrome and when will you see the warning?
Chrome has turned on the Always Use Secure Connections setting by default. The result: a full-tab message appears before a public site without encryption is opened. The schedule is in Google’s post on HTTPS by default: Chrome 147, released in April 2026, switched the option on for people using Enhanced Safe Browsing protection, and Chrome 154, released on 22 September 2026, turned it on for everyone by default. You can still go through. But first you have to click to agree, knowingly.
This variant of the setting covers public sites only. Addresses on private networks (a router panel, an office printer) stay outside the warning, because such devices usually do not have a trusted certificate anyway.
Why does a padlock on the home page not settle the matter?
Because the warning applies to each address separately. A secured main site protects neither subdomains nor old campaigns. And one more thing: a visit over http that immediately redirects to https is also treated by Google as an insecure interaction, one that until now was completely invisible to the visitor. We covered the basics, meaning the SSL certificate and redirect together with the mixed content problem, in a separate article. This one is about what is left outside them.
And the business impact? Simple. A customer clicked a link in an email, scanned a code from a leaflet or came in from an ad, and instead of your offer they see a browser message. Some people will simply close the tab at that point, because Chrome’s warning about an unsecured site looks like a sign that something is wrong with the company.
Where a site without HTTPS usually hides: a list of addresses to inventory
Old http addresses rarely sit in the main site. They usually stay somewhere off to the side, in places nobody has opened for years. Most often these are:
- a subdomain without HTTPS: a test version, a former store, a blog set up along the way,
- landing pages built for campaigns that have ended,
- login panels and webmail,
- separate domains redirected to the company one.
A single source will not give you the full list. You need to put several together: the DNS zone, the hosting panel, and the history of ad campaigns and mailings. While you are at it, I recommend reviewing which subdomains on your company domain exist at all and who is responsible for them. Many of them were set up by former contractors, and after that nobody looked at them again.
Links outside the site: email footers, print and QR codes
Http addresses also live outside the website, in materials you cannot fix with a single change on the server. The first group is email: employee footers and signatures, newsletter templates, automatic messages from the store or booking system. Each of these has to be opened and corrected by hand. Tedious, but there is no other way.
The second group is print: business cards, leaflets, packaging, signage and the QR codes placed on them. You cannot change what is printed. So the target address has to respond over https, and the redirect has to work correctly and without unnecessary hops. Add to the list your social media profiles, the company listing in maps, industry directories and entries on partner sites.
Internal links, redirect chains and external resources
Within the site itself, trouble comes from links hard-coded with http and from redirects that pass through an unsecured address on the way. Such links sit in content, menus, the footer and old posts, often dating back to before a migration. Since you are tidying them up anyway, check right away how the internal links between pages are arranged.
An http redirect chain typically looks like this: the address without www leads to the www version, still over http, and only that one leads to https. Every hop over an unencrypted connection is a potential warning. So there is one goal: a single redirect straight to the target address. Check external services separately, meaning link shorteners, forms, booking systems, embedded widgets and tracking addresses in mailings. They can start from http.
How to check company addresses step by step?
The quickest test? Turn on the Always Use Secure Connections setting in your own Chrome and go through the company addresses. Google recommends that administrators do this now. You will see exactly what customers see.
- Turn on the setting in Chrome, in the privacy and security section.
- List the subdomains and additional domains from the DNS zone.
- Open each address typed in by hand with the http prefix.
- Click through the links from email footers and scan the QR codes from printed materials.
- Search the content database for the string “http://”.
- Check the redirects for the number of hops.
- For each finding, decide: a certificate, a redirect or switching the address off.
Unneeded subdomains are better switched off than maintained. Each additional one means a certificate, updates and oversight. If the list of addresses turned out long, a review like this can be commissioned as part of a website audit, and certificates for subdomains and email are worth sorting out together with the person responsible for hosting.
Every site without HTTPS that you find and fix in a review like this is a warning the customer will no longer see. And the inventory itself usually takes less time than explaining to your audience later why the browser is blocking access to a company address.
Frequently asked questions
Will the Chrome warning appear if the http address redirects to https right away?
The first visit still goes over an unsecured connection, and these are exactly the navigations Google points to as a problem that was invisible until now. So wherever you can, fix the link or the printed address itself so that it starts with https from the beginning. In the remaining cases, shorten the redirects to a single hop and test the address with the setting turned on.
Does the change apply to panels and devices on the company network?
No. The variant of the setting that is turned on by default covers public sites, and addresses on private networks, such as the configuration panel of a router or a camera, are excluded from it. It is different for panels reachable from the internet, for example webmail on a subdomain. Those require a certificate.
What to do with a subdomain that nobody uses anymore?
It is best to switch it off. Or redirect it over https to the current address, if external links still lead to it. Remove the DNS entry when it is not needed. Because an abandoned subdomain is not only a future warning, but also an address that nobody updates.








