You have until July to Install SSL or Google will mark your site “Not Secure”

18 Jun You have until July to Install SSL or Google will mark your site “Not Secure”

A secure web is here to stay

For the past several years, we’ve moved toward a more secure web by strongly advocating that sites adopt HTTPS encryption. And within the last year, we’ve also helped users understand that HTTP sites are not secure. By next month Google will be marking a larger subset of HTTP pages as “not secure”. Beginning in July 2018 with the release of Chrome 68, Chrome will mark all HTTP sites as “not secure”

In Chrome 68, the Omnibox will display “Not secure” for all HTTP pages.

At Techinnovar we have been transitioning our clients’ sites to HTTPS and making the web safer for everyone. In conjunction with Google, we are dedicated to making it as easy as possible to set up HTTPS. Mixed content audits are now available to help companies migrate their sites to HTTPS in the latest Node CLI version of Lighthouse, an automated tool for improving web pages. The new audit in Lighthouse helps companies find which resources a site loads using HTTP, and which of those are ready to be upgraded to HTTPS simply by changing the subresource reference to the HTTPS version.

Chrome’s new interface will help users understand that all HTTP sites are not secure, and continue to move the web towards a secure HTTPS web by default. HTTPS is easier and cheaper than ever before, and it unlocks both performance improvements and powerful new features that are too sensitive for HTTP.

What do I need to do?

Worry not, Techinnovar is here for you. We install an SSL certificate and migrate your website to HTTPS. Before you order one though, take stock of what you need to secure. You may just have a single domain or you may have something more complicated like sub-domains or even multiple domains, in which case you’ll want to find the right certificate. Don’t worry, there’s a diverse set of offerings that cover just about every use case. Next, we migrate to HTTPS, by changing the protocol in your URLs to HTTPS, then using 301 redirects.