Chrome 68 Not Secure Label: Every HTTP Site Is Now Flagged

When Google sets itself a goal, it rarely backs down. Two years ago, the search giant committed to securing the web by pushing site owners and developers to adopt HTTPS encryption, and it announced the July 2018 deadline months in advance. Since late July 2018 and the release of Chrome 68, Google has gone a step further: every site that doesn’t use HTTPS now carries a “Not secure” label in the address bar.

Thanks to its near-monopoly in search, Google largely sets the rules for webmasters, developers, and site owners when it comes to website security. This new step flips the convention that existed until now. Instead of highlighting sites encrypted with HTTPS (with the padlock or the word “Secure”), Google now flags sites that aren’t, with a “Not secure” label. Click the label and you’ll see this message:

Your connection to this site is not secure. You should not enter any sensitive information on this site (for example, passwords or credit cards), because it could be stolen by attackers.

Why Move Your Website to HTTPS?

The change may look minor, but it says a lot about Google’s determination to secure the web and push webmasters to HTTPS. The warning is also worth reading because, in extreme cases, a fake site could pose as the site you meant to visit and trick you into handing over personal information.

HTTP also has privacy implications. On an unencrypted site, attackers and your internet service provider can see not only which site you’re on but also which specific pages you visit. HTTPS prevents that.

More Changes Coming in September and October 2018

The July update is just one step in Google’s HTTPS push. In September, with Chrome 69, Google plans to drop the “Secure” label next to HTTPS sites (HTTPS being the expected default). Then, in October, with Chrome 70, it will show a red “Not secure” warning when you start typing data into a form on an HTTP page.

Good for SEO, Too

One last reason to consider moving to HTTPS: encryption is one of the many factors Google takes into account to rank websites in organic search. Be careful to migrate properly, though, because poorly handled redirects can seriously hurt your rankings (broken links, wrong redirects, and so on). Search Console can now warn you when an HTTPS migration goes wrong. Référenceur is a French-speaking SEO agency from Belgium and Luxembourg that works with U.S. businesses remotely: request a free assessment for advice or to migrate your site from HTTP to HTTPS the right way.

To dig deeper:

• Google Chrome now labels HTTP sites as “not secure” (Wired)
• Why HTTPS matters (Google)
• Chrome 70: Symantec certificate distrust could take your site offline

Where Things Stand in 2026

HTTPS has become the default across the web. In 2023, with Chrome 117, Google even replaced the padlock with a neutral “tune” icon, since a secure connection is now simply expected. HTTP pages still get the “Not secure” warning, and Search Console’s HTTPS report shows which of your URLs are still served over HTTP.