Chrome 62, SSL Certificates, and What It Means For You

Starting in October 2017, Google Chrome is introducing a new update (Chrome 62) that is cracking down on web pages that are not secure. Web pages that accept user input and have URLs that begin with “HTTP” instead of “HTTPS” will generate a “Not Secure” warning in the address bar. That little “S” can make all the difference for a user to continue with you online. The “S” in HTTPS stands for secure and means that your data is encrypted with the help of an SSL (Secure Sockets Layer) Certificate. Why the change? Google’s end goal is to show a “Not secure” warning for all HTTP pages and encourage the adoption of more secure pages. ~ 9to5google.com In plain English, Google hopes to make browsing the internet more secure for everyone, and warning visitors about unsecured web pages is how they’re throwing their weight behind that goal. Why should I care? First, this new update will affect all websites’ traffic, not just Chrome users. In fact, Google says that they’ve already seen a 23% reduction in traffic to unsecured HTTP pages. Why? The simple answer is trust. If you were to enter your credit card or personal information on a website that

---