Google to Remove Green Secure Indicator for HTTPS Pages

Google made an announcement earlier today that they are to remove the security indicators for HTTPS pages starting from the Chrome version 69 that is to be released in September 2018.

Emily Schechter, Chrome Security Product Manager says since the HTTPS traffic evolved it is not required to draw user attention with security indicators, the default unmarked state is the secured one.

Instead, they are to mark the HTTP pages as not secure with a strong red warning and from the version Chrome 70 they are to flag as “not secure” when the user enters data into HTTP pages.

A secure web is here to stay! Chrome will mark all HTTP sites as "Not secure" in July 2018. 🔐⚠️ https://t.co/hcIqQvYHUM

— Chrome (@googlechrome) February 8, 2018

Chrome says the progress of moving with encrypted traffic is incredible.

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

Another massive change is with the certificate that was issued by Symantec, all the Symantec SSL/TLS certificates will stop working will stop working from Chrome 70 that to be released on Aug 30th, 2018.

Google treatment of HTTP pages cames to effect starting from Chrome version 56, with the chrome 56 the HTTP pages with password field & credit card field marked as not secure.

Starting from version Chrome 62, browsing HTTP page in Chrome incognito mode, password field and any input field marked as Not Secure.

From Chrome 68(July 2018) all the HTTP pages will be marked as Not Secure and they are intended to mark all HTTP pages as affirmatively non-secure in the long term.

According to transparency report, encrypted traffic across Google is 93% and it varies by the country and the top sites running default with HTTPS.

“We hope these changes continue to pave the way for a web that’s easy to use safely, by default. HTTPS is cheaper and easier than ever before, and unlocks powerful capabilities — so don’t wait to migrate to HTTPS!.”