In 2017, Chrome marks HTTP pages as non-secure

According to Google Security Blog,

Beginning in January 2017 (Chrome 56), we’ll mark HTTP pages that collect passwords or credit cards as non-secure, as part of a long-term plan to mark all HTTP sites as non-secure.

So, Since January 2017 If your HTTP pages contain password/credit card field, Chrome will marks them as  non-secured.

This is just a first step in their plan to make Internet more secure. In the next move, they plan to label all HTTP pages as non-secure.

So, Do you have a plant to make your Web to be more secure in 2017 ?

If you are not, You would be interested in  Let’s Encrypt project as a free SSL solution.

From: Google Security Blog 

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.