Responding to Heartbleed

heartbleed logo
Click to enlarge

We’ve continued to receive inquiries from hosting clients concerned about the Heartbleed vulnerability. As previously mentioned, our shared hosting OpenSSL version was never vulnerable to Heartbleed, and thus didn’t necessitate re-keying/re-issuing SSL Certificates for our domains because the private keys and other server data was not in a position to be compromised.  Online diagnostic tools checking for the heartbleed vulnerability may have appeared inconclusive about our server because they are testing only for the use of any version of OpenSSL, and if the issue date of the SSL Certificates was later than Heartbleed became known.  To avoid any confusion by auditors or the public, we have taken the extra step of having our hosting server’s SSL Certificate reissued so the external tests will not show a false positive.