Much of the web has switched to secure links—that is, when you type in a site like pcworld.com , it serves its pages over an https (“hypertext transfer protocol secure”) connection rather than over non-secure http. But not every website operator has yet.

From a security standpoint, http leaves users open to exploits. Try to load an http connection and you open a window for bad actors to insert exploits, malware, or social engineering attacks.

The development team at Chrome knows this is a problem, so in one year, the browser will shift its approach. Starting in October 2026 with the release of Chrome 154, Chrome will disallow all http connections by default.

But wait , you might be saying. I’ve already seen Chrome flag sites as a privacy error for not being served over https . Yep,

See Full Page