Published: Fri, February 09, 2018
Science | By Hubert Green

Chrome will start marking HTTP sites as 'not secure'

Chrome will start marking HTTP sites as 'not secure'

Three years ago, Google's search engine began favoring in its results websites that use encrypted HTTPS connections.

The warning notification will appear next to the address bar.

"Chrome's new interface will help users understand that all HTTP sites are not secure, and continue to move the web toward a secure HTTPS web by default", Google explained in a draft blog post due to be published today and provided in advance to The Register. This should further push the owners of these websites to upgrade with HTTPS encryption, which provides protection against information interception and malware injection.

In simpler words, HTTPs ensures that the communication thread between your browser and the website you're surfing can not be breached by anyone else.

However, Schecter says that other groups may be more affected by the change.

Google is not alone in its decision to penalize all HTTP sites.

HTTPS is the secure version of HTTP, or Hyper Text Transfer Protocol.

Google has been purging non-HTTPS-enabled websites for a very long time.

What Does HTTPS Encryption Do?

Slated for release in July, this transition comes as 68% of all traffic on Android and Windows is now protected, while that number jumps to 78% on Chrome OS and Mac.

Google has recently announced that with the release of latest version of Chrome, Chrome build 68, all HTTP sites will be labeled as "not secure". As Google explains, "When you load a website over HTTP, someone else on the network can look at or modify the site before it gets to you". If you are not aware about protecting your website, you can follow the official setup guidelines offered by Google for your website.

Later on, with Google Chrome 62, the giant has protected the pages which opened via HTTP on a secure browsing mode with not secure label. Google has tried to make the Internet a more secure place for everyone, giving developers and administrators the opportunity to switch to HTTPS from HTTP.

Like this: