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:
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: