The Chrome browser shall mark all HTTP Sites as “not secure” beginning July 2018. This follows the release of Chrome 68 version.
Google said on its official blog post that Chrome was dedicated to “making it as easy as possible to set up” HTTPS. Mixed Content audits were 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 new audit in Lighthouse helped developers find which resources a Site loads using HTTP, & which of those are ready to be upgraded to HTTPS simply by changing the subresource reference to the HTTPS version.
Chrome’s new interface will help users understand that all HTTP Sites were not secure, & continue to move the Web towards a secure HTTPS Web by default.
Image Credit: Google