HTTP Changes in Google Chrome 62 for October 2017
Google announced that it is stepping up its efforts against non-HTTPs sites – or sites without an SSL certificate – starting in October 2017. In October 2017, Google’s Chrome browser will start marking sites as “Not secure” if they are running HTTP instead of HTTPS.
Here is a view of the two major changes coming in Chrome 62.
Treatment Of HTTP Changes In Chrome 62
The first is that HTTP pages with user input are going to be marked “Not secure” starting with Chrome 62 in October 2017. The second is that browsing in Chrome Incognito mode will mark all HTTP sites as not secure starting in October 2017.
The bottom line is this, your business can’t afford to wait on transitioning to HTTPS today, and we can help you do that quickly and painlessly.
We Take The Confusion Out Of Installing Let’s Encrypt SSL Certificates
This package will audit the SSL capabilities of your server or hosting package and provide your best options to get compliant with Google’s requirements, including installing a Let’s Encrypt certificate, if possible. Let’s Encrypt is a new SSL certificate service created by Google and Facebook to encourage the adoption of the HTTPS protocol on all websites. Unlike most SSL certificates, there are no annual or renewal fees for Let’s Encrypt, so once it’s installed and configured correctly, you’re covered now and in the future.
If your host allows Let’s Encrypt SSL certificates, we will go ahead and install and configure it for you at no additional charge.
If your host doesn’t allow Let’s Encrypt, we’ll provide you with your best options to get compliant with Google’s requirements.