{"id":47529,"date":"2018-01-04T13:00:00","date_gmt":"2018-01-04T19:00:00","guid":{"rendered":"https:\/\/blog.cpanel.com\/?p=47529"},"modified":"2018-01-04T13:00:00","modified_gmt":"2018-01-04T19:00:00","slug":"avoiding-a-not-secure-warning-in-chrome-heres-how","status":"publish","type":"post","link":"https:\/\/devel.www.cpanel.net\/blog\/tips-and-tricks\/avoiding-a-not-secure-warning-in-chrome-heres-how\/","title":{"rendered":"How to Avoid a \u2018Not Secure\u2019 Warning in Chrome"},"content":{"rendered":"

UPDATE! On February 8th\u00a0Google announced<\/a>\u00a0on their blog they’re going to start alerting in July 2018 for non-SSL sites. Get your SSL today!<\/strong><\/p>\n

\n

As TLS and SSL set a new benchmark for securely browsing the internet, devices and web browsers are equally raising the bar for presenting users a safe experience. As part of this effort, Google Chrome now displays a \u201cNot Secure\u201d warning in the web address bar when users visit a website without a valid SSL certificate. In the current version of Google Chrome (v63), this warning will only appear when entering information into a form, or if the browser thinks you’re trying to submit any type of secure information like login names and\u00a0passwords. This warning will\u00a0eventually occur on\u00a0any<\/em>\u00a0HTTP page, but no timeline has been established.<\/p>\n

What’s the difference between HTTP and HTTPS? What is the importance of TLS and SSL?<\/h2>\n

HTTPS encrypts the communication between a web server and the browser. By browsing via HTTPS (using TLS\/SSL ciphers), we can prevent interference and intrusion such as injected advertisements and stolen data like passwords or credit card numbers. Any traffic sent unencrypted can be read and even modified by anyone between you and the website.<\/p>\n

Learn more:\u00a0Why HTTPS Matters – Google Web Fundamentals<\/a><\/em><\/p>\n

What will users see if they try and browse via an insecure HTTP connection?<\/h2>\n

At this current time, Google Chrome browsers will be prompted that their connection is insecure any time the browser thinks you’re\u00a0sending or receiving\u00a0sensitive information. The warning may not appear immediately when browsing to a website. For example, when trying to log in to a website over HTTP, the browser will warn the user via the address bar only after the login field has been selected.<\/p>\n

\"Non-secure<\/p>\n

Want to see how your browser reacts to a variety of insecure situations? Check out the Chromium Project’s testbed:\u00a0https:\/\/badssl.com<\/a><\/em><\/p>\n

While a safer browsing experience is important to all users of the internet, there are some hosting providers and website owners that this will impact\u00a0more than others. For example:<\/p>\n