A milestone for Chrome security: marking HTTP as “not secure”
With the latest release of Chrome 68 the browser will now begin pointing out that sites are NOT secure rather than promoting those that are. Technically, nothing different will happen, however, it will cast doubt in users minds when they notice something is called Not Secure.
If you’re a site owner looking to migrate (or build!) your site on HTTPS, we’ve helped make the process as simple and inexpensive as possible. Improvements include managed HTTPS for Google App Engine, required and automatic HTTPS on all .app domains, and free and automated certificates through Let’s Encrypt (Chrome is a Platinum sponsor). And if you’re in the process of migrating to HTTPS, look out for messages coming from Search Console with further information and guidance.
So when you’re shopping for concert tickets or online banking, rest assured: you’ll be warned if a site is not protecting your data with HTTPS. And we’ll continue to improve Chrome’s security, to make sure you’re using the most secure browser out there.
An excerpt from A milestone for Chrome security: marking HTTP as “not secure”
