Users are informed by Google Chrome on pages without HTTPS with the text “not secure” – in the fall, the text will then become a red warning signal.
Google marks all HTTP pages as insecure, Screenshot YouTube, © Google Chrome Developers
For Google, the implementation of HTTPS is a foundation for a secure network. Therefore, this is driven forward rigorously. While HTTPS pages have so far been labeled “secure”, this should not happen from September. For this reason, all HTTP pages will be marked as “not secure” from today on and from October even with a red warning sign.
HTTP pages on Google Chrome are no longer secure
In February, Google announced for its browser that as of July 2018, and with the launch of Chrome 68, all HTTP sites would be classified as “not secure”.
For example, pages with HTTP appear as “not safe”, for the time being, © Google
This positions you very clearly at the Alphabet subsidiary. Because only HTTPS allows the use of certain features of browsers, such as Progressive Web Apps. It is also a key factor in optimizing the loading speed. And this is finally, especially mobile, an immensely important aspect for the ranking.
Marking a secure HTTPS page in Chrome, screenshot Google
In addition, HTTPS is particularly relevant in the context of security and privacy. Google’s technical writer Kayce Basques provides comprehensive information on why Google Chrome is calling for HTTPS implementation.
According to this, the unmarked status of websites should indicate “safe” in the future. That means again that Google will remove the ad “safe” with Chrome 69 from September.
Google removes the mark for “safe” pages, © Google
Already a lot of HTTPS – but not nationwide
Overall, the use of encryption over HTTPS has been very well received. Just over ten days ago, according to Google, the number of pages loaded in Google Chrome over HTTPS was 83 percent in Germany.
As early as the beginning of the year, it was announced that 81 of the top 100 sites in the network were using HTTPS, and that the sites considered “safe” were in the range of two-thirds of all. These values are likely to have changed further today. However, there are still a lot of sites that Chrome does not get the seal “safe”.
Starting today, all pages will be clearly marked with HTTP. And this kind of brand becomes even more drastic. So far, so Google, the HTTP use was still too high, as that one could mark all these sides with a red warning signal. But that’s exactly what will happen with Chrome 70 from October 2018.
So, according to Emily Schechter , product manager at Chrome Security, it should already be ensured that all webmasters tackle the implementation of HTTPS. So that a safer and possibly even faster network is promoted. These requirements should become the standard; and Google Chrome provides with its tags for it. Because even if the users do not pay too much attention to the markings “safe” and “not sure”, they are more likely to do so when a warning signal appears in red.
If you do not yet have encryption over HTTPS, at least for Chrome should now build on it. Google itself gives tips on how this can be done.