Outfits like Google, Let’s Encrypt, cPanel and Comodo are pushing for a more secure Internet.
Obviously there is nothing wrong with that, and I commend them (and others) for pushing and supporting for this.
In this case we are talking about adding a so called SSL certificate to websites, allowing encryption, which can be identified by the url starting with “https”. In other words making the good old and regular “http” protocol secure.
In the past one would have to pay yearly to keep the SSL certificate valid, for every single domain, or pay even more for so called wildcard certificates. But, for basic purposes, this is no longer the case (for commercial use one still will have to pay for a certificate) – thank you Let’s Encrypt and Comodo for providing those free certificates.
Now keep in mind though that we have nothing critical here at Tweaking4All that would need encryption. However, in the push for website owners to start using encryption, Google has seemed to have gone the route where their browser will display messages that may look misleading to the end-user, for those website that do not support encryption. Not even mentioning the possible negative Google ranking impact for websites that are not encrypted.
So I’ve spend the better part of this weekend to implement SSL/HTTPS on Tweaking4All as well – it has caused some problems, and possible downtime and odd behavior of the website in the past 2 days. My apologies for that … you should now see a green “Secure” message near the address-bar of your browser.
Please feel free to report issues, or moments where this does not show a green “Secure” indicator – it’s not impossible that I overlooked one or the other small piece.