Chrome browser will mark all non-SSL sites ‘Not Secure’ in July

You may have noticed the lock icon with the words ‘Secure’ for most of the websites you visit in Chrome. Not very long ago, most of the top websites switched over to always using SSL encryption for your connection. For the most part, these SSL connections have been used mostly only when performing sensitive transactions involving information such as user logins and credit card transactions in order to encrypt the data so that it is unable to be intercepted by third parties on its route between you and the web server.

In July for update 68, Google Chrome will be marking any sites not using HTTPS (SSL) as ‘Not Secure’. This is a step in the right direction, in my opinion. The entrance to using SSL encryption has become very easy with services such as LetsEncrypt, which allows you to easily set up valid SSL encryption for your website.

Although SSL connections require a little bit more processing power and bandwidth to be utilized, the difference is negligible by current technology standards. For this reason, the huge benefits of encrypting all of the traffic between you and any server is worth the benefit. I firmly believe that most everything you do over the internet should be sent by encrypted means. There is a lot of layers between you and your information’s intended destination.

As a side note, one type of protocol I often see overlooked is the FTP protocol. By the standard FTP protocol, your login information is sent un-encrypted over the internet when you use this protocol. Instead, I recommend using SFTP (SSH File Transfer Protocol) for FTP exchanges as it is much more secure and usually already included in any type of server setup.

Leave a Reply

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