Skip to main content

If a site is not HTTPS, Google Chrome will tell users it's not secure

The tech giants of the world are continuing their efforts to make the web a safer place, and Google Chrome is leading the charge. On Thursday, the Silicon Valley tech giant announced that Chrome will begin marking HTTP pages as nonsecure if they collect passwords or credit card information. This, the company hopes, will encourage more sites to move toward HTTPS — and otherwise adhere to general security guidelines — in order to secure their traffic.

“To help users browse safely, Chrome indicates connection security with an icon in the address bar,” Google explained in its Chromium blog. “Historically, Chrome has not explicitly labeled HTTP connections as nonsecure,” but that changes starting in version 56. Over the next few weeks, site visitors will be warned when they land on an HTTP instead of HTTPS site — this is “part of a long-term plan to mark all HTTP sites as nonsecure,” Google said.

Recommended Videos

Google has long held influence over the state of the web — both on desktop and mobile. Last year, the internet behemoth announced that it would start knocking sites if they weren’t mobile responsive, which lowers their search ranking. This certainly helped to spur an increase in mobile-responsive sites, making it easier for smartphone users to browse the web on their handheld devices.

Security is more important than ever, particularly given the increasing frequency with which breaches and hacks now occur. Google Chrome’s decision to begin explicitly marking insecure connections is aimed squarely at the issue.

Separately, Chrome 56 will also allow sites to interact with Bluetooth Low Energy (BLE) devices using the Web Bluetooth API across operating systems, including Android, Chrome OS, and Mac. As per the Chromium blog, web developers will be able to “connect to bluetooth devices such as printers and LED displays with just a few lines of JavaScript.” 

And finally, the latest version of Chrome will support CSS position: sticky, a new way to position elements. The blog explains, “A position: sticky element is relatively positioned, but becomes position: fixed after the user reaches a certain scroll position … Now, users can achieve the desired effect by simply positioning their elements as sticky.” 

Lulu Chang
Former Digital Trends Contributor
Fascinated by the effects of technology on human interaction, Lulu believes that if her parents can use your new app…
This underrated Google Chrome feature turned me into a power user
google chrome automatic tab groups featured

I don't like when my web browser pesters me. It's one of the many reasons I use Google Chrome over Microsoft Edge, but for once, I'm actually thankful to catch a stray pop-up in Chrome.

You may have seen a similar pop-up in Chrome, assuming you consider it the best browser, like I still do. When your tab count gets unmanageable, Chrome will offer to group your tabs together. I dismissed this notification probably a dozen times, but I decided to finally give it a shot one day. And it completely changed how I use Chrome.
The time saver

Read more
This upcoming AI feature could revolutionize Google Chrome
Google's Gemini logo with the AI running on a smartphone and a PC.

One of the latest trends in the generative AI space is AI agents, and Google may be prepping its own agent to be a feature of an upcoming Gemini large language model (LLM).

The development, called Project Jarvis, is an AI agent based within the Google Chrome browser that will be able to execute common tasks after being given a short query or command with more independence than before. The inclusion of AI agents in the next Chrome update has the potential to be the biggest overhaul since the browser launched in 2008, according to The Information.

Read more
Google blocks popular ad blocker for ‘security and privacy concerns’
A MacBook with Google Chrome loaded.

Millions of Chrome users might soon lose access to their favorite extensions. As mentioned in Google's support bulletin, Google plans to end support for popular ad blockers such as uBlock Origin and other extensions on the Manifest V2 framework. Google says the move is because of security and privacy concerns.

Google started warning users of the change back in August, stating that it plans to move from the Manifest V2 framework to V3 to protect its users. Google says that it's doing this "to better protect your privacy and security, Chrome and the Chrome Web Store require extensions to be up-to-date with new requirements. With this, Chrome may disable extensions that don't meet these requirements."

Read more