Google's Official Warning - Encrypt by July

The move by browsers to warn visitors that webpages served via HTTP are "Not Secure" has been underway for a while. Some businesses have acted quickly, gotten a security certificate and encrypted their websites (changed to HTTPS protocol).

But some of us leave changes till the last minute. Well, the last minute has come.

What's Changing

Google Chrome 68 has been launched and it marks all webpages without a security certificate (SSL/TLS certificate) as "Not Secure".

Over the past year, Google and Mozilla have marked HTTP webpages as insecure only if they used unencrypted passwords (log in pages) or text fields (online forms). Expect other browsers to follow Google's lead for all webpages.

Why the Change?

An HTTP website is not secure in transit. Data travelling the Internet (from static page content to credit card numbers) can be stolen or manipulated. That's a big risk.

HTTPS transmission is secure; encryption authenticates the web server and protects all the transmitted information. It's easy to understand why web browsers want it as a basic standard. So should all of us - website owners and website visitors.

HTTPS is faster, and boosts search engine visibility compared to the same webpage on HTTPS.

How Do I Get HTTPS?

Contact your web developer/managed webhosting service to have an SSL/TLS certificate installed on your website asap.

Website security is about more than encrypting data. Security certificates can also offer identity validation to assure site visitors that they are on a website run by a genuine business, not a scam or a fly-by-night operator.

Choosing the right SSL certificate can be confusing. We're here to help.

More info on website SSL/TLS certificates