Execute Order 62: The Great Google Chrome ‘Not Secure’ Website Purge

In a galaxy far far away, Supreme Chancellor Palpatine executed Order 66, also known as Clone Protocol 66. The order, unbeknownst to my 6-year-old self from 1983, branded the Jedi as traitors to the Republic. The clone army, loyal to the republic, swiftly executed the order, resulting in the purge of the Jedi.

Not all hope was lost. The last Jedi, Luke Skywalker, helped bring peace to the galaxy and balance to the force. 30-some odd years later, like Luke, Google is trying its best to help protect us from the Palpatine’s of the internet.

The Internet of things (IoT) is vast network of interconnected devices, enabling them to send and receive data. Some of this data contains sensitive information such as your login and credit card information. In January 2017, Google Chrome version 56 started labeling pages as ‘Not Secure’ whenever a input field for login or credit card information was present.

As of October 2017, Google Chrome version 62 will label any page as ‘Not Secure’ if users can input any data in any kind of field over an unencrypted connection.

Is your site secure?

Here are a few questions to ask yourself:

  1. Does your site receive any user input? This includes contact forms, search bars, surveys, logins, etc.
    Is your website using HTTP:// in the address bar?
  2. If you answered “yes” to both of those questions, you need to install an SSL certificate to avoid showing a ‘Not Secure’ warning on your website. You should also force HTTPS to avoid users from accidentally accessing a non-encrypted version of your website.

Need help installing an SSL certificate for your website? Contact Ross Media Solutions Today!