Google will remove the green padlock

Last Update: May 21, 2018

In the new version 70 of the Chrome browser that is scheduled for October this year, Google has announced that they will remove the green padlock marking of secure sites.

This is done because SSL certificates are easy to use and available for all, and secure HTTPS is now more or less the standard for websites and users now expect that sites are secure.

Google says on their Chromium blog on May 17th that earlier the HTTP usage was too high to mark unsecured sites in an efficient way. Therefore Google chose to mark secure sites with the green padlock.

This has now changed and HTTPS sites by far outnumber HTTP sites.

The green padlock will be replaced by a 'Not secure' warning when the user enters data in a form on a non-HTTPS site.

So there will be no warning for a non-secure HTTP site until the user starts to interact by filling in a form. Since all the SSL encryption does is to encrypt data transfers from forms, this means that the warning will appear where and when it's needed.

When you start to fill out a form on a non-HTTPS site, there will be a red warning sign where the green padlock now used to be.

Chrome will roll this change out over time.
In the current Chrome 67 version, HTTPS sites are marked with a green padlock.
In Chrome 69, planned for September this year, secure sites will be marked with a grey padlock.
For Chrome 70 the secure marking will completely disappear.

In February Google stated on their Google Security Blog that this change will appear already in Chrome version 68 that is planned for July this year.

But whatever the timeframe will be, the padlock is going away.

This does not mean that we should forget to install SSL on our sites. We should be as thorough as before on this matter. But the only page or post that users will be warned about non-HTTPS is where an interaction takes place.

Sources:
Google Chromium Blog
Google Security Blog

Join the Discussion
Write something…
Recent messages
bryanb007 Premium
Thanks for the helpful info
Reply
JHaugland Premium
Thanks
Reply
Loes Premium
I have read about it, I wonder how the siterubix websites will display
Reply
ABeckles Premium
Best guess is it will be treated as an HTTP site. So you will probably get the warning label on siterubix sites.
Reply
Loes Premium
That's no good for business
Reply
JHaugland Premium
They will be treated as HTTP, and will show no warning except for pages and posts with forms.
Reply
JHaugland Premium
Is it actually any change from what the situation is today on free siterubix?
No SSL is available, so there is no green padlock, and a big insecure warning if you are unlucky.
Reply
Loes Premium
Real unlucky when they show that popup
Reply
NScholz Premium
Interesting! I will have to check this later when I have more time. Right now I am in a rush. Thank you for sharing this.
Reply
JHaugland Premium
Thanks
Reply
codevonish Premium
Thanks for sharing.Will WA be taking care of any changes
Reply
JHaugland Premium
No changes are needed, and we don't need to do anything else than what we already do.

The only change that may happen is that SSL will be installed by default and we don't have to switch it on. But I have no idea if that is something that is in the plans of the WA-crew.
Reply
UrsaMajor Premium
Thanks for this informative post! I am very happy to hear this news!
Reply
JHaugland Premium
Thanks for reading
Reply
Top