Chrome will now mark HTTP as ‘not secured’

Chrome will now mark HTTP as ‘not secured’

Starting from the launch, Chrome has been promising the users about their security. Because security has been one of Chrome’s core principles since the beginning.

When you’re browsing a website over plain HTTP, your connection to the site is not secured. Which means anyone on the network can look at any information going back and forth, or even modify the contents of the site before it gets to you. So, it’s important for every developer to make sure that their website is served to the user over HTTPS. With HTTPS, the connection made between the user and your website is secured and gets encrypted, so that the information transferred back and forth will only be available for your server and the user. Chrome has been helping developers for this. Chrome would warn every user with the ‘not secured’ mark when the browser cannot establish a secure connection with that particular website. Using the warning badge Chrome warns the user as well as motivates the site’s owner to improve the security of their site.

Google Chrome was only marking ‘not secure’ to websites over HTTP only when the user enters any data to the site like credit card number or passwords. But, recently Google Chrome Team announced some new features coming up. Starting from this September, Chrom will remove the “Secured” tag from all the HTTPS websites. And in October, Chrome will mark every plain HTTP websites with red “not secure” when the user enters data to the site.

Read more on Google Blog