Effective July 2018, Google’s Chrome browser will mark non-HTTPS sites as ‘not secure’.
After years of pushing for ‘secure by default’ web sites, Google will identify insecure sites in the Chrome browser beginning mid-Summer.
July is shaping up to be a big month for #Google. Earlier this month, the company announced its Speed Update set to roll out in July, and then announced it will then also mark all sites that have not migrated to HTTPS as “not secure.”
“For the past several years, we’ve moved toward a more secure web by strongly advocating that sites adopt HTTPS encryption. And within the last year, we’ve also helped users understand that HTTP sites are not secure by gradually marking a larger subset of HTTP pages as “not secure”. Beginning in July 2018 with the release of Chrome 68, Chrome will mark all HTTP sites as “not secure””, announced Chrome’s Security Product Manager.
Google has been pushing webmasters to make the change to non-secure web sites a for years now – including hinting at small rankings boost to further incentivize the shift.
The campaign has proved successful.
#Google notes that 81 of the top 100 sites on the web now use HTTPS by default and that over 78% of Chrome traffic on both Chrome OS and Mac is now protected. Over 68% of Chrome traffic on both Android and Windows is now protected.
Chrome is dedicated to making it as easy as possible to set up HTTPS. Depending upon the size of a site and scope of the project, a migration from HTTP to HTTPS can be quite an undertaking.
Chrome’s new interface will help users understand that all HTTP sites are not secure, and continue to move the web towards a secure HTTPS web by default.
HTTPS is easier and cheaper than ever before, and it unlocks both performance improvements and powerful new features that are too sensitive for HTTP.