StartCom has been a key player for years in the landscape of SSL certificate providers with its 'StartSSL' services. They provided free SSL certificates for everybody and permitted a lot of small organizations to increase the security of their web communications. The fact that StartCom is a China-based company was, for some organizations, a good reason to flag their activities as suspicious. They also suffered from security incidents. In October 2016, Mozilla decided to remove the StartCom certificates from Firefox. Google did the same with Chrome in March 2017.
The termination of services is now officially scheduled (for the 1st of January 2018). Here is the official message sent to customers:
As you are surely aware, the browser makers distrusted StartCom around a
The browsers imposed some conditions in order for the certificates to be
StartCom will stop issuing new certificates starting from January 1st, 2018
StartCom would like to thank you for your support during this difficult
StartCom is contacting some other CAs to provide you with the certificates
Please let us know if you need any further assistance with the transition
StartCom Certification Authority
I searched across my SSL activity logs and I found 5 websites still using a StartSSL certificate. If you're still using StartSSL certificates for some websites, it's time to move to an alternative provider. We highly recommend having a look at the Let's Encrypt project.
Xavier Mertens (@xme)
Dec 3rd 2017
1 year ago
That email is hilarious.
>Considering this situation, the owners of StartCom have decided to terminate the company as a
"the owners of StartCom have decided" no everybody else decided, you had no say in it.
And look at this
>StartCom is contacting some other CAs to provide you with the certificates needed
Oh great, they're going to put my email address on sixteen other spam lists. Thanks, StartCom.
This is a good thing, the company should have been dead a year ago. These are the same people (under the name WoSign) that gave out github.com certs to anyone who asked, claimed they had "fixed the issue" four months later, and actually had just added "github.com" to a blacklist without fixing the underlying tech issue.
Dec 3rd 2017
1 year ago