Google moves closer to encrypted web

Friday, 1 June, 2018

As part of Google’s ongoing strategy for an encrypted web, Chrome will now mark all HTTP pages that do not display the green secure lock with a red ‘Not Secure’ warning.

As far back as 2014 Google had proposed that Chrome would initially mark only HTTP pages requesting passwords or financial details as ‘Not Secure’, but promised to eventually mark all unencrypted pages in the same manner.

Four years later, more than 93% of the traffic using Google resources employed an encrypted connection. This is in comparison to just 50% in 2014.

Just three years ago around 40% of the loaded pages were using HTTPs. With around 75% of pages loaded via Chrome now served by HTTPS, Google has its eye on complete elimination of unencrypted connections.

For the past several years, we’ve moved towards a more secure web by strongly advocating that sites adopt HTTP encryption. And within the last year, we’ve helped users to understand that HTTP sites are not secure by gradually marking a larger subset of HTTP pages 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.

Users should expect that the web is safe by default, and they’ll be warned when there’s an issue. 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.

We hope these changes continue to pave the way for a web that’s easy to use safely, by default. HTTP is cheaper and easier than ever before, and unlocks powerful capabilities, so don’t wait to migrate to HTTPs.

- Emily Schechter: Product Manager, Chrome Security

The latest announcements are part of Google’s push for more webmasters to adopt HTTPs as a secure encryption standard for data in transit.

This means any data from your computer to a website is transmitted securely and is protected from attackers.

HTTP wraps a secure tunnel around a site and its user while the encryption also serves to ensure the content hasn’t been modified by any attacker.

Google is not the only internet company to push for the adoption of HTTPs. WordPress started offering free HTTPs to all hosted websites, while Amazon is offering free security certificates to AWS customers.

TG Bamford author picture

By:

A veteran freelance journalist writing extensively on internet news and cybersecurity.

News What's the story?

Keep up with the latest developments in UK broadband.

KCOM buyout means more fibre for Yorkshire

Hull's homegrown ISP sells for more than half a billion.

KCOM buyout means more fibre for Yorkshire Read more

Virgin gigabit trials begin in Southampton

Nationwide gigabit takes a big step forwards with Virgin's new network upgrade.

Read more

Tesco customers get triple value with NOW TV

Get the most out of your Clubcard points with streaming discounts.

Read more

CityFibre bring full-fibre to 70,000 homes

Only 4.9 million to go...

Read more

Help Learn with us

Make the most of the internet with our broadband library.

What are the risks of using public WiFi?

What are the risks of using public WiFi? Read more

How to optimise WiFi connections in old buildings

Read more

How to choose a broadband provider you’ll be happy with

Read more
Back To Top