Chrome will start marking all HTTP sites as not secure in July
Feb 12 2018
If you are completely unaware about this, Google is also offering a complete setup guide which will show you the importance of encryption and why HTTP is not secure in the current technology era. Mixed content audits are now available to help developers migrate their sites to HTTPS in the latest Node CLI version of Lighthouse, an automated tool for improving web pages, " the Google blog post read.
Chrome holds 59 percent of the global browser market share across mobile and desktop, according to NetMarketShare. And now they say time's up as the next rollout of Chrome will mark all those sites that are still on HTTP as "not secure". Chrome 56, released in January 2017, started marking HTTP pages that collect passwords or credit cards as "Not secure".
The warning follows with a link redirecting to Google's support page on how to determine if a website's connection is secure.
As a result of those efforts, 68 percent of Chrome traffic on Windows and Android systems is now protected with HTTPS, Schecter said. Chrome users should now be discouraged from giving out their personal information when seeing the "not secure" tag.
The second stage took place with Chrome 62 when Google marked all HTTP pages opened in a Private Browsing window as "Not Secure". The search giant revealed that more than 78 per cent of Chrome traffic is now protected on Chrome OS and Mac. Yes, you will no longer be able to directly surf such websites through your Google Chrome web browser as Google is limiting such fake users and websites owners who are taking advantages and run illegal websites to earn money.
Google has been pushing the web to HTTPS for years, but it accelerated its efforts last year by making changes to Chrome's user interface.
Unlike Google, the Mozilla Foundation did not announce a deadline when it planned to activate this new policy.