Chrome 68: A Big Reason to Switch HTTPS

Chrome 68’s release in July 2018 gives publishers a major push to switch to HTTPS. On its Security Blog, Google recently announced that all HTTP sites will be marked as “not secure”. It’s the latest in a large chain of steps that Google has taken to drive HTTPS adoption across the web.

Here’s what the omnibox will look like in Chrome 68 compared to previous versions:

In the same post announcing Chrome 68’s treatment of non-secure sites, Google also shared the following strong numbers illustrating how rapidly websites have been adopting HTTPS:

  • More than 68% of Chrome traffic on both Android and Windows is protected under HTTPS
  • Over 78% of Chrome traffic on both Chrome OS and Mac is HTTPS compliant
  • 81 of the top 100 sites on the web use HTTPS by default

Avoiding the non-secure label is only one of the several reasons for publishers to move to HTTPS. Discover all of them in our free eBook below:


For more information on the importance of migrating to HTTPS, see our articles on the impact that WPA2 had on HTTPS, the wider role HTTPS plays in a free web, or why websites without forms even need to migrate.

We will continue to keep you updated on the latest developments like these, so be sure to subscribe to updates from our newsletter in the form below:

Leave a Reply