Securing your Website Properties with HTTPS is the Smart Decision.

SSL or Secure Sockets Layer protection is usually implemented in the following scenario: When you wish to secure your website content along with user and customer data – when providing ecommerce services.  Generally speaking to encrypt credit card data when the client is paying onsite (on the website itself) for a product and/or service during the checkout process.

The definition by is:  SSL (Secure Sockets Layer) is the standard security technology for establishing an encrypted link between a web server and a browser. This link ensures that all data passed between the web server and browsers remain private and integral.


Browserweb offers shared and managed web hosting services.


With Google ranking “secure” websites, we are happy to announce that all our servers now have the “Lets Encrypt” SSL icon in your cPanel.

What is Lets Encrypt? It’s an open source (Free) SSL Certificate provider and you can learn more on their website.

We have been patiently waiting for months for cPanel to release their Lets Encrypt plugin (as this is the Control Panel we have installed on your web hosting) and the first major release has made it’s way out of BETA. Browserwebs’ network engineers have installed this wonderful addon to our servers and I am delighted to announce it is working like a charm. You don’t need to install anything, it’s already setup for SSL.  Rest assured, everyone can now enjoy https secure websites and you’ll be loved by Google and your customers. 


As with any product, the difference between free and paid is all in the level of security, features and support.  For anyone running a commerce or ecommerce website, I strongly suggest a commercial certificate and dedicated IP purchase for your website.  If you’re running a blog or a general website, then the Lets Encrypt SSL is the perfect solution.



The purpose of this article is to enlighten clients, visitors and interested parties about the basics. I assume you’ll hire your webmaster to do the extensive checklist required for established websites to make it to https without any hiccups.  For an example of what questions and concerns arise, you can read this article by Google Webmasters on HTTP to HTTPS and the FAQ’s listed therein: Migrating to HTTPS

Although it’s really quite straight forward, it can have bumps in the road, especially with larger sitemaps and websites. The main areas that a client should consider are items like sub-domains, CDN, .htaccess and rewrite rules.  Some or all of these tasks can create head-scratching issues and a few choice words to boot!  That’s just part of a developers daily life, finding out why the migration worked seamlessly on one website and yet was a myriad of warnings and bugs on another.  It’s one of these projects that you want to go smoothly but sometimes there’s a bite in the process somewhere when you thought it was all looking so good.  Like I say, depending on the size of the website in question, one always recommends a development server check rather than working on a live website.


With SSL everyone is happy.  Your content and encryption is good which keeps data a lot more safe than just HTTP.  It’s another obstacle for hackers to overcome.  On top  of that, there’s the added bonus that Google and search engines will show you some more respect as well by perhaps giving your ranking a wee booster.

Apart from the decision to actually switch to HTTPS, once you take the plunge, there really are ZERO negatives.

Remember, if you need assistance feel free to #sayhello (@browserweb on twitter) or email me personally if you have any questions or comments.


Mark Burke, a Digital Media Company