SSLs.comReviews 10,128

Customer service seems responsive, and they make an effort to provide a solution it seems. Thank you.

As per some random feedback

It took an hour to really grasp the differences between all the types of SSL certificates; wasn't sure at first if there were some that were more secure or could handle a DDOS attack for example. I got the main differences pretty quick (ie:, EV, wildcard, etc), but some of the more advanced differences took a while to figure out on my own. It would of been nice to have a more comprehensive and down to earth over view of why you might go with a more expensive option.

I did the file-upload option for the auth, and wasted hours waiting for it to work. After spending some time Googling, I finally found out that it won't work over HTTPS, only HTTP -- which left me dumbfounded. Wish this was made more clear; also seems a bit silly to only support HTTP and not HTTPS too considering it all.

I didn't feel I had very clear instructions on how to deploy the SSL certificate provided; linux/apache. I also didn't feel that there was enough clear instruction on how to properly secure the SSL certificate. If you do not modify Apache's config file, the SSL certificate will remain vulnerable to exploits.

There was also no recommendation towards newbies on simple ways to deploy an SSL certificate, such as using Amazon's load balancer service. For someone unsure how to setup an SSL certificate, recommending such easy options would be valuable.

It would be great if a service could be provided as part of the purchase to check the certificate every once in a while automatically to see if the site is secure and not vulnerable. If the site isn't secure, email me with instructions on how to fix it.