#Security

Still not on HTTPS? We have some bad news.

Posted on 01 Sep 2017

When Google Chrome reaches version 62, which will happen in October 2017, even more HTTP sites will be marked as "not secure".

This is part of long-term effort of encouraging transition to the "secure by default" web which started with version 56. That Chrome version started showing warnings in address bar on HTTP sites with login and payment forms. Mozilla Firefox followed similar approach soon.

After Google Chrome version 62, warnings will expand to all HTTP websites containing any form element. So, technically, even the websites with search or contact form will be marked as unsafe. Since trend is clear, and HTTPS is already at tipping point in acceptance, it is strongly recommended to consider moving your website(s) to HTTPS as soon as possible.

Other Blog Entries

#Security

Usernames You Don't Want On Your System

Author Marsmedia HQ 01 May 2013

#Security

How to secure your online accounts and data

Author Srdan Stojkovic 15 May 2018

Contact

Whether you have a question, suggestion or feedback, our team is always here to assist you. We believe that communication is key to building strong and long-lasting relationships, and we are committed to providing you with the best possible support.