All HTTP sites are now being marked as ‘not secure’ by Google Chrome

Google Chrome Security

Google Chrome Security

Google Chrome security has recently stepped up its game and marked all HTTP sites as ‘not secure’. As part of moving towards a more protected web, Google hopes that this strong avocation will be enough to persuade all sites to eventually adopt the HTTPS encryption.

HTTPS encryption protects the channel that exists between your browser and the website that you’re visiting which ensures that nothing can tamper with the traffic or keep tabs on what you are doing. If this encryption system did not exist, anyone with access to your router or ISP could intercept information that is sent between, including personal passwords.

This decision was not made abruptly, as Google Chrome has taken steps towards higher security over the past year.

“We’ve [been helping] users understand that HTTP sites are not secure by gradually marking a larger subset of HTTP pages as ‘not secure’, explained Chrome security product manager Emily Schechter.

The updated version 68 of Google Chrome will now warn users with an extra notification in the address bar of the browser when they are using an HTTP site, while HTTPS-encrypted sites receive a green lock icon to notify the user that the site they are visiting is secure to use.

Yet, this shouldn’t come as a surprise for Google Chrome users, as the company has been slowly drifting away from unencrypted sites for years by down-ranking them and instituting regular warnings for password fields.

Needless to say, the increased Google Chrome security new system adoption was brought on due to the already existing encrypted Google traffic to HTTPS sites, with 81 out of the top 100 sites on the web already defaulting to HTTPS.

This search giant is keeping its promise and making the internet a safer place for users.

What do you think of this update in Google security? Tell us all about it in the comments section below.

2 thoughts on “All HTTP sites are now being marked as ‘not secure’ by Google Chrome

  1. Just want to make sure I understand this correctly. We just need the Https when someone is entering information on the site, correct? Such as log in, account areas, things like that.



Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Chat with us Contact Account Cart Search Cart Open Menu Arrow Link Arrow Chat Close Close Popup