Chrome Takes A Step Further Towards A More Secure Web

It seems that 2016 might be the year, when HTTP might finally die.
Chrome security have gone on to announce that the Browser will start marking the Websites, which uses insecure HTTP connections, so as to transmit the passwords and credit card data as insecure, starting January 2017. The warning will go on to appear in the address bar of the Browser and will attract the attention of the users, to the possibility that their personal information can be stolen or spied on.
 
 
Chrome in its official blog states,
 
“To help users browse the web safely, Chrome indicates connection security with an icon in the address bar. Historically, Chrome has not explicitly labelled HTTP connections as non-secure. Beginning in January 2017 (Chrome 56), we’ll mark HTTP sites that transmit passwords or credit cards as non-secure, as part of a long-term plan to mark all HTTP sites as non-secure.”
 
Finally, Chrome will go on to add the security warning to HTTP pages and whenever a user visits them in the Browsers “Incognito” mode and it will in the mean, while warn the will roll out to all the HTTP pages.
 
The changes seems to go on to indicate, that is to pressurize the site owners to change to a more secure HTTPS, which goes on to encrypts the data, while it is being in transit and helps it to prevent the site from being modified by the malicious users.
 
The company states,
 
“A substantial portion of web traffic has transitioned to HTTPS so far, and HTTPS usage is consistently increasing. We recently hit a milestone with more than half of Chrome desktop page loads now served over HTTPS. In addition, since the time we released our HTTPS report in February, 12 more of the top 100 websites have changed their serving default from HTTP to HTTPS.”
 
The company informs that they plan to label HTTP sites ‘clearly and accurately’ and starting January 217, Chrome 56 will go on to label HTTP pages with the password or credit card form as “not secure”.
 
The company concluded by stating,
 
“In following releases, we will continue to extend HTTP warnings, for example, by labelling HTTP pages as “not secure” in Incognito mode, where users may have higher expectations of privacy. Eventually, we plan to label all HTTP pages as non-secure, and change the HTTP security indicator to the red triangle that we use for broken HTTPS.”