Chrome 68 Update Could Mark Your Site As “Not Secure”

Posted by Shruthika Kamat on June 15, 2018 at 1:13 PM

Chrome 68 is set to come out starting July 2018 and could have serious implications for businesses still running their sites on HTTP. This includes not only losing site traffic, but also driving away customers and prospects. The solution to preventing this issue is HTTPS.

What could this mean for businesses? 

This could be bad news for businesses still running on HTTP. In the past, Google has implemented this with Chrome 56 for sites that require a login, or financial information. Soon, it will apply to any and all HTTP sites. When a visitor comes into an unsecure site, Chrome 68 will mark it as “Not Secure” right next to the URL, alerting them that any information they submit could be at risk.

In October, Google will be releasing a Chrome 70 update where all HTTP pages will be marked with the “strong red warning”  triangle and “Not Secure” text when information is being entered.

For HTTPS sites, it shows a lock with the words in green which will probably be kept in the new update, but faded out by Chrome 69 in September. Because Google is pushing for a safer web, they are going to eventually remove the lock and “Secure” text. According to Google“users should expect the web … [to be] safe by default.”

HTTP, HTTPS, What does it mean anyway?

HTTP and HTTPS are transfer protocols that essentially transfer data between servers and browsers. As users are browsing the internet, these protocols are how they see the information on a webpage. All the text, images, videos and other content. The main difference between HTTP and HTTPS is the security – how safe or hackable is your website?

HTTP stands for Hypertext Transfer Protocol, which is the standard protocol without any encryption. This means that hackers can steal any information on that site while the information is moving from browser to server, or, vice versa. Any site with this will be marked “Not Secure” by Chrome as early as July 2018.

HTTPS stands for Hypertext Transfer Protocol Secure, which encrypts all information being transferred. Hackers can still access the information, but it will be really difficult for them to decode and use it against anyone. This is what the Chrome 68 update is pushing for all sites to have.

“ Beginning in July 2018 with the release of Chrome 68, Chrome will mark all HTTP sites as “not secure” ”
– Emily Schechter, Chrome Security Product Manager


I’m not using Chrome though…

Chrome may not be the main browser for businesses and their tasks, but a little over 60% of the market uses Google Chrome on Desktop/ Laptop, Mobile and Tablet. It dominates all the other browsers since 2016. In other words, securing sites are almost necessary for the amount of traffic that Chrome receives.

The Solution

Securing your site doesn’t have to be difficult for you. Here are two easy steps for you to get your site in the right place before Chrome 68’s release in July 2018.

  1. How do I know if I have HTTPS?

    An easy indicator is going up to the top of your browser where your URL is and checking if it says “Secure” in green with a green lock.


  2. What if my site is marked unsecure as of now?

    No worries! There are many resources to get yourself registered. Its recommended to contact your web host and discuss your need for an SSL certificate.

If your site isn’t secure, what else hasn’t been secured yet? Make sure it’s safe by contacting us for a free IT Audit.
FREE IT Security Audit


Tags: Tags: , , , ,