Starting with the Chrome 68 browser. Chrome 68 will label all HTTP sites as “not secure” when it is released in July.
Google is quick to point out that the move to HTTPS has been happening at a rapid pace over the past few years and provided the following statistics:
- 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
It should be noted that Google Chrome is by far the most popular browser on the planet, so that should be incentive enough for developers to act fast. It is Google’s hope that with a little additional prodding, internet users will be further protected during their everyday browsing. Google first began the transition from HTTP to HTTPS by “flagging” websites that didn’t use encryption when collecting credit card information and passwords.
Emily Schechter, Chrome Security Product Manager says:
“HTTPS is easier and cheaper than ever before, and it unlocks both performance improvements and powerful new features that are too sensitive for HTTP.”
For developers that need a little additional help in making the transition, Google asks developers to scour its setup guides and to check out mixed content audits to help ease the migration process.
