Monthly Archives: Feb 2018

HTTPS – encrypt your website now

For the past several years, Google has been strongly advocating that sites adopt HTTPS encryption. Within the last year, users of Googlge Chrome will have noticed that Google has been  gradually marking a larger subset of HTTP pages as “not secure”.

At the moment users will only see the ‘not secure’ warning on pages where personal details are collected, such as forms, or on purchase pages. However, beginning in July 2018 with the release of Chrome 68, Chrome will mark all HTTP sites as “not secure”.

Chrome currently indicates HTTP connections with a neutral indicator. This doesn’t reflect the true lack of security for HTTP connections. When you load a website over HTTP, someone else on the network can look at or modify the site before it gets to you.
 
A substantial portion of web traffic has transitioned to HTTPS so far, and HTTPS usage is consistently increasing. More than half of Chrome desktop page loads are now served over HTTPS. 
 
All our new websites use https protocol by default, and we are in the process of converting all our client sites at no cost to the client.