Buy from the highest-rated provider   Buy SSL.com Certificate x

Sectigo SSL Certificate Reviews

Sectigo is a privately held company that offers SSL certificate and computer security products. It was previously known as Comodo and Comodo CA but has since been sold to new owners and changed its name to Sectigo on November 1st, 2018. It was founded in 1998 and is headquartered inĀ Roseland, New Jersey USA.

The Sectigo SSL certificate reviews listed below will help you determine whether Sectigo is a good company to buy SSL certificates from. The reviews have been verified to be from real Sectigo customers.

If you want to compare Sectigo SSL certificates with certificates from other SSL providers, use our SSL Wizard. If you have ever purchased or received a certificate from Sectigo, please post a Sectigo SSL review to let others know what to expect.

4.53 (4477 Total Reviews)

Sectigo Reviews

Showing review 1 to 20 of 4518 | Next | Last

Keith Reynolds

Keith Reynolds

EV certificate issues
August 4, 2020 Permalink
Overall Rating:
Product: Several different products

Over the past month, I have had a few issues with the EV certificate issued 1.5 years ago to Brentmark Software. Last month, I had to change the parameters in the SignTool command prompt (took me a while to figure out why it was not working on my end - once I saw the update on the site with changed parameters, it worked fine). Its been about a month or so since we released anything, and last night I tried to sign an executable - the signing got to through several phases, but then 'hung' at the last step where its signed. For 5-10 minutes. Finally it reported an error message. It then froze my machine, restarted and contacted support today. I called in initially, because when i went to the site https://sectigo.com/knowledgebase and typed in SafeNet, and clicked first link, it told me that the ticket team was working on the site, but to call in... so, called in, and the guy said that they could see the site properly. He couldn't diagnose that problem, much less the problem that I was having with the code sign itself. Luckily, I also 'chatted' with a consultant you have there 'Grace' was her name - we went back and forth for a good while (30-40 minutes), and we came up with a solution to try to install a fresh SafeNet client on a different machine, along with a fresh install of Windows Kit. She was able to send me the direct link to download the Safenet client, and after installation, I was able to run the sign tool from the windows kit and it properly signed the executable. So, we determined the issue was either with an outdated SafeNet client or the Windows Kit was out of date (corrupt). So, kudos to Grace for helping.

Showing review 1 to 20 of 4518 | Next | Last

Advertisement • Hide