September 11, 2016

Google to scare the visitors of unencrypted websites

Chrome to kill HTTP

Emily Schechter from the security desk of Google has posted on Google's official blog that how will they scare the visitors of unencrypted websites in the coming versions of Google Chrome.

An unencrypted website uses HTTP (Hyper Text Transfer Protocol) to transmit data between users and server. This type of protocol is insecure, any third party usually termed as "third man" connected to the same network can steal and modify the data before it gets to the visitor.

Exploiting your unencrypted connection to the server, an attacker will also be able to steal your sensitive data like your credit card's information or any password you type on any website which uses HTTP to transfer the data.

Currently, Chrome 53 shows a neutral sign in the address bar when you visit a website over HTTP connection. This sign doesn't scare any visitor and no one leaves the website because of that. To make visitors take HTTP connection seriously, Google decided to replace that icon with a red colored triangle. This will scare the traffic of HTTP websites for sure and people will avoid filling password fields on such websites.

Chrome will roll this out gradually. Starting from January 2017,  Chrome 56 will mark HTTP websites containing password or credit card form fields as insecure. The following releases will start marking all HTTP pages as insecure in Incognito mode.

Chrome 53 & Chrome 56 address bar

And then it will be the time when all HTTP pages will be labeled as "not secure" along with the red triangle icon.

Treatment of HTTP pages by Chrome

Schechter also wrote that more than half of the Chrome desktop pages are being served over secure HTTPS connection. Furthermore, she wrote that almost all top websites are over encrypted connection.

Google have given webmasters a few months before they will start scaring their traffic. Having encrypted connection will be the only choice to make visitors trust your website in future. So consider switching to HTTPS now.
About Author:
is the founder of AskTechnologist. He is a web developer & designer, SEO consultant, cyber security researcher, and a technology geek. He can be reached on Facebook, Twitter, LinkedIn & Google+.
Share this story:


Post a Comment