Google Chrome will start labeling HTTP websites as non-secure

Gradually, Google is pushing website owners to deploy HTTPS. Chrome 56 should be released in January 2016, when it will start showing in the address bar a warning that labels sites that transmit passwords or credit cards over HTTP as non-secure.

HTTP nebezbedan u Chromeu

In due course, Chrome will start labeling all HTTP pages as non-secure, and in final stage the HTTP security indicator will turn red, and sport the “Danger!” triangle with which sites with broken HTTPS are currently marked:

Google Chrome http nebezbedno

Google wants to encourage all website owners to switch from HTTP to HTTPS to keep everyone safe on the web. That's why Google is already using HTTPS as ranking signal.

Google Chrome security team noted that "A substantial portion of web traffic has transitioned to HTTPS so far, and HTTPS usage is consistently increasing".

“We recently hit a milestone with more than half of Chrome desktop page loads now served over HTTPS. In addition, since the time we released our HTTPS report in February, 12 more of the top 100 websites have changed their serving default from HTTP to HTTPS.”

So, if you own or manage websites that transmit passwords or credit cards over HTTP, it's about time get SSL certificate.

Domain validated SSL certificates, from $49:

Thawte SSL123GeoTrust Quick SSL PremiumRapidSSL

Organization validated SSL certificates, from $199:

Thawte SSL Web ServerSymantec Secure SiteGeoTrust True BusinessID

Extended validation SSL certificates, from $299:

Thawte SSL Web Server with EVSymantec Secure Site with EVGeoTrust True BusinessID with EV