Editor’s Note: If you were partnered with Longevity Technology, this issue would have been addressed months ago. Contact us today!!

Google Chrome users who visit unencrypted websites will be confronted with warnings from tomorrow.

The changes will come for surfers using the latest version of Google Chrome, version 68. Any web page not running HTTPS with a valid TLS certificate will show a “Not secure” warning in the Chrome address bar from version 68 onwards. The warning will apply both to internet-facing websites and intranet sites accessed through Chrome, which has approximately 60 per cent market share.

google_chrome_warning Google Chrome: HTTPS or bust. Insecure HTTP D-Day is tomorrow, folks

In Chrome 68, the address box will display “Not secure” for all HTTP pages.

The Chrome update is designed to spur sites still stuck on HTTP to move over to HTTPS, as Google explained back in February. The web has made great strides in that direction of late but much work is yet to be done.

Security luminary Troy Hunt is developing a site called whynohttps to coincide with the Chrome 68 launch. The site will list the world’s largest websites that don’t do HTTPS by default.

Hunt and his colleague Scott Helme are looking to list HTTPS laggard sites by industry sector, a task they’d like some help in automating, as well as country. Hunt explained in a Twitter update: “For people offering support on this, I’ve sorted the country data, but what I really need now is data on the category of the site. Is there any service that says ‘Baidu is a search engine, Fox News is media, etc’?”

The majority (542K) of the top one million sites do not redirect to HTTPS and will therefore be labelled as insecure from tomorrow onwards, Cloudflare warned.

Running secure sites is not only for the big boys and is not necessarily expensive. Letsencrypt certs are free. Aside from the security benefits of preventing pages from being tampered while in transit, HTTPS has commercial benefits for site owners too. Both browsers and search bots favour HTTPS sites.

5f111cbaa05662491e9e2468a26fd364_normal Google Chrome: HTTPS or bust. Insecure HTTP D-Day is tomorrow, folks

The Register

@TheRegister

Your website’s static, has no login forms nor any sensitive content on it, so it doesn’t need HTTPS? *Wrong* Not only do browsers and search bots favor HTTPS sites, it prevents your pages being tampered with while in transit@Letsencrypt certs are free https://letsencrypt.org/how-it-works/ 

F56mUitY?format=png&name=144x144_2 Google Chrome: HTTPS or bust. Insecure HTTP D-Day is tomorrow, folks

How It Works

The objective of Let’s Encrypt and the ACME protocol is to make it possible to set up an HTTPS server and have it automatically obtain a browser-trusted certificate, without any human intervention….

letsencrypt.org

Although Chrome is the first mainstream browser to affix high-visibility warnings system to non-HTTPS websites, it’s likely that Microsoft, Apple and Mozilla will follow suit. ®

via Google Chrome: HTTPS or bust. Insecure HTTP D-Day is tomorrow, folks • The Register

Subscribe To Our Newsletter

Join our mailing list to receive the latest news and updates from our team.

You have Successfully Subscribed!

Share This