Google continues to take steps to mark all HTTP pages as "Not secure"

Google keeps steps to mark all HTTP pages as "not safe."
In January last January, Chrome continued its series with a more secure network, Chrome started displaying the "Not Sure" label on those pages that received less credits of passwords and cards for the HTTP connection application. And now they have announced their next phase.

From October 2017, some types of data (not only for passwords and cards) can be applied on HTTP pages and when used in the integration mode using the browser, TT is always displayed under HTTP. Will happen The final goal is that at some time all HTTP pages are tagged. These gradient steps are not lightweight and based on research that have been done on customer behavior, see the "Sand Connection Connection Security Indicator".

Chrome is not the only browser that has taken action in that direction, Firefox is also doing this directly with AdWords that directly requests the form and card passwords.
Google keeps steps to mark all HTTP pages as "not safe."
In January last January, Chrome continued its series with a more secure network, Chrome started displaying the "Not Sure" label on those pages that received less credits of passwords and cards for the HTTP connection application. And now they have announced their next phase.

From October 2017, some types of data (not only for passwords and cards) can be applied on HTTP pages and when used in the integration mode using the browser, TT is always displayed under HTTP. Will happen

The final goal is that at some time all HTTP pages are tagged. These gradient steps are not lightweight and based on research that have been done on customer behavior, see the "Sand Connection Connection Security Indicator".

Chrome is not the only browser that has taken action in that direction, Firefox is also doing this directly with AdWords that directly requests the form and card passwords.

Password in Firefox with http

It is important to remember that after browsing under HTTP connections can increase many different concepts that are confidentiality. An attacker, for example, can insert or modify the page to taste the advertisement, may also change malware injection or information that users are currently viewing.

Instead, when a connection is made under HTTPS, user computers travel in a hidden form on a web or application, offering more security and privacy. While it is true that even under HTML TTP attacks can be made on connections, they are more complicated for forwarding and organizers or able to strengthen security through webmaster HSTS and HPKP policies.

Finally, the SSL certificates can be easily accessed and free today, using one of these Cloudflare, although it presents some boundaries and the other independent way is using tea encryption, one Certification Authority, which calculates the help of diverse companies including Google, between Facebook, Mozilla, Akama, others.

On the SEO or search engine positioning level, a switch in HTPP is like domain change and is not a complicated thing to do so. Generally, if everything gets well, positioning remains in it.