At the end of January 2017, Google Chrome web browser version 56 will be unleashed, marking a big change in how the browser presents sites not using HTTPS, which is based on an extra security layer. Sites that continue to avoid purchasing the SSL certificate and ask for passwords or credit card numbers will be accompanied with the message “not secure” in the location bar.
Here are more details about Chrome’s shift toward identifying ecommerce sites that do not provide adequate protection.
Google Chrome moves to outdate HTTP
The new Chrome update is the first step in a series designed to replace HTTP with HTTPS. Users will see “not secure” messages in the Incognito mode of Google Chrome for non-HTTPS pages, as this mode is used by people who have a high expectation of privacy. For site owners, this message may be confusing for users who misinterpret it as a security vulnerability with an immediate threat.
The “not secure” message will also appear on login pages that lack the SSL certificate. Web hosts are encouraging site owners to purchase HTTPS upgrades, especially for sites that collect confidential information.
Eventually, Chrome will show a warning on any pages that are not secured with an SSL certificate.
Google is consistently looking for ways to improve the search experience of its users, particularly when it comes to safer browsing. Version 56 is part of a long-term plan to address the privacy and security concerns of online shoppers. HTTPS helps guard against attackers and intruders that tamper with site communications.
This extra security layer helps prevent the website from being misused and has been adopted by hospitals, hotels and other large organizations.
Site owners still using HTTP
HTTP site owners that want to protect their reputation from the confusion that will likely occur from the new browser upgrade should start by reviewing support documentation provided by their web host. Look for the section on SSL certificates. You may find it more advantageous to have the web host set it up for you, since configuring it yourself can lead to complications.
Google provides instructions for implementing SSL to your website, but it may be too technical for some people that don’t want to take the time learn the jargon related to this upgrade. It’s usually faster and easier to consult your web host’s support documentation or to contact a support representative. You may also want to run a Google search on “SSL installation” to learn more from digital marketers and bloggers how to keep your site from getting tagged as “not secure.”
The target release data for Chrome version 56 is January 31. The release may not be on that exact date, but it will mark a new way that non-HTTPS site will appear in the Chrome browser. HTTP sites will appear with “not secure” messages to warn users that the site does not have maximum security protection. Owners that want to protect their integrity and avoid being tagged as “not secure” should consult with their web host and upgrade the hosting service to include an SSL certificate.