Google’s Chrome Browser to Mark Non HTTPS Sites as ‘Not Secure’
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.
For the past several years, Google have moved toward a more secure web by strongly advocating that sites adopt HTTPS encryption. And within the last year, they also helped users understand that HTTP sites are not secure by gradually marking a larger subset of HTTP pages as “not secure”.
Developers have been transitioning their sites to HTTPS and making the web safer for everyone. Progress last year was, according to Google, ‘incredible’, and it’s continued since then:
• Over 68% of Chrome traffic on both Android and Windows is now protected
• Over 78% of Chrome traffic on both Chrome OS and Mac is now protected
• 81 of the top 100 sites on the web use HTTPS by default.
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. Developers, check out our set-up guides to get started.