Google Search Console has already started sending out notices to web sites that have not migrated yet to the HTTPS protocol. Google Chrome version 61 is currently in BETA and the developers are now preparing the version 62.
Once the Google Chrome 62 will be launched, it will start marking HTTP pages as “NOT SECURE.” This will happen sometime in October 2017, which means that the webmasters still have enough time to make their web sites more secure by using HTTPS.
After installing Google Chrome 62 on your computer, when the web browser detects any forms on the page that transmit credit cards, passwords or any kind of text input field, it will automatically warn you that you are surfing on an unsecure web page and your credentials might be stolen.
HINT: At the same time, all HTTP web pages in incognito mode will trigger the same warning.
We remind you that starting from January 2017, Chrome version 56 has started marking web sites that transmit passwords or credit cards as non-secure, as part of its long-term plan to mark all HTTP web sites as non-secure. It seems that this warning will get even more prominent in time. Google has started sending emails to webmasters to fix this problem as soon as possible.
We have to mention that most companies that are hosting WordPress web sites have added Let’s Encrypt integration to offer free certificates to customers. Since this year, WordPress is recommending only hosting partners that provide SSL certificates by default. Currently there are over 60% of web sites that are using HTTPS and it is just a matter of time until more and more will start using this protocol.
Will you keep filling forms with your credit card, bank account, passwords on a web site that is still using the HTTP protocol?