The latest version of the Google Chrome browser, version 68, introduced a new “Not Secure” warning in the address bar that appears anytime you are visiting an insecure web page.
The warning refers to the shortage of security for the connection thereto page. It’s alerting you that information sent and received thereupon page is unprotected and it could potentially be stolen, read, or modified by attackers, hackers, and entities with access to internet infrastructures, like Internet Service Providers (ISPs) and governments.
HTTPS also provides protection against malicious people impersonating an internet site, for instance, if you’re on a public Wi-Fi hotspot and hook up with Google.com, Google’s servers will provide a security certificate that’s only valid for Google.com. If Google was just using unencrypted HTTP, there would be no thanks to tell whether you were connected to the important Google.com or to an imposter site designed to trick you and steal your password. for instance , a malicious Wi-Fi hotspot could redirect people to those sorts of imposter websites while they’re connected to the general public Wi-Fi.
The “Not Secure” warning is being displayed on any page served over HTTP, which is an insecure protocol. If you’re seeing this warning on a site you own or operate, you ought to resolve it by enabling the HTTPS protocol for your site
HTTPS uses the SSL/TLS protocol to supply a secure connection, which is both encrypted and authenticated. Using HTTPS requires that you simply purchase an SSL certificate(s), then you’ll install that certificate and enable the HTTPS protocol on your web server.
What to do ?
If you’re the technical administrator or developer for your site, you ought to begin by assessing if you currently have any support for HTTPS. Some sites have partial support, meaning they need deployed HTTPS to some parts of the location , or haven’t chosen to serve the location via HTTPS by default. If either is that the case, check out what steps got to be taken to deploy HTTPS across your entire site and by default. Our guide to configuring HTTPS Everywhere will assist you start .