Sectigo SSL Certificate Reviews

Bought a certificate and Comodo just added a SAN to my certificate without asking. Contacted chat support: did not understand my issue and just said it is not possible and closed the session without asking if I am happy with that response. If you need a cheap simple certificate you can use Comodo. Comodo has the longest Trial certificates (90 days) but validation is limited to WHOIS lookup and default mail addresses. No dedicated/new admin contact. If you need good online support and have more complex certificate requirements you should think twice.

I purchased the license and had a little trouble with the installation so I contacted Comodo's live chat service on their website and the technician had me up and running in less than an hour. The certificate works well and my site is as fast as ever.

After the first installation I found out the ssl analyzer report say "not vakidated by MS and Mazilla". Due to some server problems (common name mismatch" I requested re-issuance of ssl ALSO requested "if not MS and Mazilla approved, refund my order" (in one week period I studied the differences). The second time my ssl was MS and Mazilla approve. Maybe it was a bad co-incident BUT I will never trust blindly any more.

Couldn't believe how streamlined the Instant SSL Certificate was... all I had to do was secure the site's contents such as images and the certificate was enabled for me. Literally just plug and play!

I really appreciate comodo. This i the best certificate i have ever used.

I recommend COMODO SSL cert, they are very reliable and easy to install and issue within seconds, and their support is very competitive.

Comodo are probably the cheapest and fastest way to get your SSL cert

It took almost two months, around 20 emails and days and days of wasted time to get my code signing certificate. Really, trust me, don't do it, unless you enjoy dealing with witless idiots.

I purchased a Comodo PositiveSSL cert through a reseller who offered it for considerably less money than buying direct from Comodo. The process was straightforward: submit a CSR, answer a confirmation email sent to a domain contact address, and the cert was issued. The whole process took around 15 minutes. Added perk: Comodo will sign your cert using SHA2 (with all SHA2-signed intermediate certs chaining back to the root) if one adds the appropriate flag ("-sha256") to OpenSSL when generating a private key/CSR. For example, this command will generate a 2048-bit RSA key and request a SHA256 signature: "openssl req -new -newkey rsa:2048 -nodes -sha256 -out www.mydomain.com.sha256.csr -keyout www.mydomain.key"

Our certificate expired, even though we paid our host, who handles our certificate, the day of our notice. Yes,minor solace, we received an apology. None the less, our site was down for days, we spent many hours trying to resolve, plus our app was not able to properly access the server. In short, we were Out of Business!Dead in the water. Kaput! Last week's fried chicken. Well, you get the idea. We also had to temporarily switch to HTTP instead of HTTPS, resend HTTP versions of our app to Beta testers, etc., etc. All this at very considerable time and expense. All of this could have been easily avoided if we had been able to pay for the SSL Certificate in advance. For instance, a two-year payment. Also, one would think that Comodo would require host providers to "provide" a means to notify SSL Certificate holders, i.e., website owners in advance of an expiration. The party who holds the certificate should be able to receive advance notification directly from Comodo and make payment directly to Comodo. It is entirely unacceptable to have all these problems over a $50 certificate!