Google gears up to mark all HTTP pages as 'not secure'

From September 2018 Google will no longer display HTTPS pages as secure in its Chrome browser, in a move that further cements its position to make all websites secure by default.

Last week Chrome Security product manager Emily Schechter explained that internet users should expect that webpages are safe by default – and they will only be told when there's an issue.

Previously, we posted a proposal to mark all HTTP pages as definitively "not secure" and remove secure indicators for HTTPS pages. HTTPS usage on the web has taken off as we've evolved Chrome security indicators. Later this year, we'll be taking several more steps along this path," Schechter says in the blog.

Google first announced its efforts in September 2016, and has since completed two phases towards making all pages HTTPS secure.

Currently Google Chrome marks all HTTP pages as not secure if they have password of credit card fields. It also shows HTTP pages as not secure when users enter data, and when users visit HTTP pages through incognito mode.

According to a blog from February 2018, more than 68% of Chrome traffic on Android and Windows is protected. 78% of traffic on Chrome OS and Mac is also protected. In July 2018 the third phase will mark all HTTP pages as not secure. In September 2018, all HTTPS will be marked as neutral rather than secure.

Schechter explains what these changes mean for users:

"Since we'll soon start marking all HTTP pages as "not secure", we'll step towards removing Chrome's positive security indicators so that the default unmarked state is secure. Chrome will roll this out over time, starting by removing the 'Secure' wording and HTTPS scheme in September 2018 (Chrome 69).

In October 2018, HTTP will be marked in red as 'not secure'.

"Previously, HTTP usage was too high to mark all HTTP pages with a strong red warning, but in October 2018 (Chrome 70), we'll start showing the red "not secure" warning when users enter data on HTTP pages," Schechter explains.

Google also says that HTTPS is now cheaper and easier than ever – some services even offer security certificates for free.

The company also points out that HTTP sites will continue to work and there are no plans to block them in Chrome; the only thing that will change is the security indicators.

"We hope these changes continue to pave the way for a web that's easy to use safely, by default," Schechter concludes.