Chrome Will Tag HTTP Websites as ‘Not Secure’ in Address Bar Whenever User Enter Details
Google is working on making its Chrome browser safer for users. The tech giant had been warning websites on using HTTPS instead of HTTP since January this year. Taking another step ahead for security, Chrome has announced that it will mark HTTP pages as “not secure” in the address bar whenever the user enters data on the web page.
The company had been using this technique with Chrome 56 that was launched in January this year. It marked HTTP sites “Not secure” whenever user entered password or credit card fields. This step by Google gained 23% decline in the use of such pages on desktops.
In its latest move, the tech giant will show “not-secure.” tag in the address bar for an HTTP site. It will appear whenever the user clicks on any data field to fill details on the website. Earlier, this tag was limited to credit card information and passwords, but now it will apply to all the data fields.
In a blog post, Emily Schechter from Chrome Security Team writes:
Passwords and credit cards are not the only types of data that should be private. Any type of data that users type into websites should not be accessible to others on the network, so starting in version 62 Chrome will show the “Not secure” warning when users type data into HTTP sites.
Same functionality for Incognito Mode
The blog post also notes that the same functionality will also be present in the incognito mode on Chrome browser. Google is expected to start rolling out the feature with Chrome 62 update that will arrive in October. With the version 62 of Chrome, Google is eyeing on encouraging more websites to start using HTTPS instead of the unreliable HTTP. The company also says that the transition from HTTP to HTTPS is cheap for the website owners and by doing so, they will also enhance the functionality of their website.
Google’s increased focus on non-secure websites is commendable and we expect that its latest announcement encourages website owners to use HTTPS protocol. Also, we would like to suggest our readers to always check whether a website is using HTTPS prefix, if not then we suggest on not sharing important details on such websites.