{"id":37628,"date":"2024-12-06T04:15:45","date_gmt":"2024-12-06T04:15:45","guid":{"rendered":"https:\/\/devwp02.visibleone.io\/vowp\/?p=37628"},"modified":"2024-12-06T07:01:41","modified_gmt":"2024-12-06T07:01:41","slug":"google-chrome-will-mark-http-sites-as-not-secure-effective-july-2018","status":"publish","type":"post","link":"https:\/\/devwp02.visibleone.io\/vowp\/blog\/google-chrome-will-mark-http-sites-as-not-secure-effective-july-2018\/","title":"Google Chrome Will Mark HTTP Sites as \u201cNot Secure\u201d Effective July 2018","content":{"rendered":"\n\n\n
\n \n

Google Chrome Will Mark HTTP Sites as \u201cNot Secure\u201d Effective July 2018 <\/h1>\n \n Website Security<\/a> Estimated Reading Time<\/span>\n 4 mins<\/span>\n
\n Updated November 28, 2023<\/span>\n Published June 23, 2018<\/span>\n <\/div>\n <\/div>\n\n\n\n\n
\n \n Blog<\/a>><\/span>google-chrome-will-mark-http-sites-as-not-secure-effective-july-2018<\/span> <\/div>\n
\n
Author: <\/span>Visibee<\/span>\n <\/div>\n <\/div>\n <\/div>\n
\n \n \"\"\n<\/span>\n
\n \"\"<\/a>\"\"<\/a>\"\"<\/a> <\/div>\n <\/div>\n \n
\n \"\"<\/a>\"\"<\/a>\"\"<\/a> <\/div>\n <\/div>\n \n
\n

Starting July 2018, with the launch of Chrome 68, Google Chrome will mark all HTTP sites or not protected by SSL as \u201cNot secure\u201d, fulfilling a plan rolled out in September 2016, in hopes of fostering a more secure web.<\/p>\n

On Google\u2019s official blog<\/a>, Emily Schechter, a Chrome security product manager said:<\/p>\n

\u201cFor the past several years, we\u2019ve moved toward a more secure web by strongly advocating that sites adopt HTTPS encryption. And within the last year, we\u2019ve also helped users understand that HTTP sites are not secure by gradually marking a larger subset of HTTP pages as \u201cnot secure\u201d. Beginning in July 2018 with the release of Chrome 68, Chrome will mark all HTTP sites as \u201cnot secure\u201d.<\/p>\n

This announcement is a huge deal. With the release of Chrome 68, here is how HTTP sites will look like in the address bar:<\/p>\n

The logic behind the change, Google explained that “users should expect that the web is safe by default.” It will remove the green padlock and “secure” wording from the address bar for every HTTP site beginning with Chrome 69 in September. This lets users know that their personal credentials are safe and secure while browsing HTTPS sites.<\/p>\n

What is the difference between HTTP and HTTPS?HTTP stands for HyperText Transfer Protocol and HTTPS stands for HyperText Transfer Protocol Secure. Both HTTPS and HTTP are protocols used to transfer data over the web. In basic terms, the difference between HTTPS and HTTP is that information sent using HTTPS is encrypted, and therefore secure, ensuring no one in the middle can tamper with the traffic or spy on what you\u2019re doing, whereas information exchanged using HTTP (note: no “s” on the end) is not secure, and it can be intercepted by third parties to gather data being passed between the two systems.<\/p>\n

HTTPS involves the use of an SSL certificate<\/a> – which provides secure, encrypted communications between a website and an internet browser. “SSL” stands for Secure Sockets Layer, the protocol that provides the encryption.<\/p>\n

This is especially important for sites where sensitive information is passed over the internet, such as e-commerce sites<\/a> with non-secure pages that accept online card payments, or login pages and online forms that require users to enter their credentials.<\/p>\n

While many websites will be affected by this, many are also in compliance. In Google\u2019s blog, it also stated that:<\/p>\n

Over 68% of Chrome traffic on both Android and Windows is now protected
\nOver 78% of Chrome traffic on both Chrome OS and Mac is now protected
\n81 of the top 100 sites on the web use HTTPS by default
\nFairly, there\u2019s no reason developers shouldn\u2019t implement it. It\u2019s cheaper and easier than ever before.<\/p>\n

Mozilla also prepares to mark all HTTP sites “Not Secure” after HTTPS adoption rises following in Google\u2019s footsteps. Jonathan Kingston, a security developer for Firefox, stated on Twitter that the company is experimenting to mark pages \u201cNot Secure\u201d in Firefox.<\/p>\n

The increased adoption of HTTPS among website operators will soon lead to browsers marking HTTP pages as “Not Secure” by default.<\/p>\n

Going back to Google, it offers an open source and a free security auditing tool called Lighthouse<\/a> that lets developers identify which website resources still load using HTTP and help improve the quality of web pages.<\/p>\n

So make sure all commercial web pages are covered by SSL and begin transitioning to HTTPS as soon as possible in order to see success in business.<\/p>\n

Move your website from HTTP to HTTPS with an SSL Certificate today!<\/p>\n

\"\"<\/p>\n<\/div>\n <\/div>\n\n <\/div>\n <\/div>\n<\/section>\n