From HEXONET Wiki
(Created page with "{{Sidebar}} <div style="font-size: 150%;">'''Comodo is now Sectigo'''</div><br/> <p> In late 2017, Comodo's CA was acquired by Francisco Partners. With this new partnership, ...") |
|||
| (One intermediate revision by one user not shown) | |||
| Line 3: | Line 3: | ||
<p> | <p> | ||
| − | + | Comodo's CA was acquired by Francisco Partners in late 2017. With this new partnership, Comodo is expanding beyond SSL and has demonstrate a renewed commitment to innovation, digital transformation and service. As a result of this, they have rebranded Comodo to Sectigo! | |
| + | <br><br> | ||
| + | Following the rebranding, product name changes will be effective starting January 2019. You'll soon start seeing certificates issued by Sectigo instead of Comodo over time. However, this change will happen gradually and seamlessly. It will not affect existing products and Comodo Authority roots will remain trusted. | ||
| + | <br><br> | ||
| + | You can see a list of product name changes in the following section below. | ||
| + | |||
| + | = Product Name Changes = | ||
| + | The product name change will be reflected on HEXONET's website and Control Panel. However, this does not affect existing API implementation or price relations. | ||
| + | |||
| + | {| class="wikitable" style="width:60% !important" | ||
| + | |- | ||
| + | ! scope="col" style="text-align:left; border:1px solid darkgray" | Original Name | ||
| + | ! scope="col" style="text-align:left; border:1px solid darkgray" | New Name | ||
| + | ! scope="col" style="text-align:left; border:1px solid darkgray" | Still using the same class name | ||
| + | |- | ||
| + | | style="text-align:left" | Comodo SSL || style="text-align:left" | Sectigo DV SSL || style="text-align:left" | COMODO_SSL | ||
| + | |- | ||
| + | | style="text-align:left" | Comodo EV SSL || style="text-align:left" | Sectigo EV SSL || style="text-align:left" | COMODO_SSL_EV | ||
| + | |- | ||
| + | | style="text-align:left" | Comodo SSL Wildcard || style="text-align:left" | Sectigo DV SSL Widcard || style="text-align:left" | COMODO_SSL_WILDCARD | ||
| + | |- | ||
| + | | style="text-align:left" | Comodo Instant SSL || style="text-align:left" | Sectigo Instant SSL || style="text-align:left" | COMODO_INSTANTSSL | ||
| + | |- | ||
| + | | style="text-align:left" | Comodo Instant SSL Premium || style="text-align:left" | Sectigo Instant SSL Premium || style="text-align:left" | COMODO_INSTANTSSL_PREMIUM | ||
| + | |- | ||
| + | | style="text-align:left" | Comodo Premium SSL Wildcard || style="text-align:left" | Sectigo Premium SSL Wildcard || style="text-align:left" | COMODO_PREMIUMSSL_WILDCARD | ||
| + | |- | ||
| + | | style="text-align:left" | Comodo Positive SSL || style="text-align:left" | Sectigo Positive SSL || style="text-align:left" | COMODO_POSITIVESSL | ||
| + | |- | ||
| + | | style="text-align:left" | Comodo Essential SSL || style="text-align:left" | Sectigo Essential SSL || style="text-align:left" | COMODO_ESSENTIALSSL | ||
| + | |- | ||
| + | | style="text-align:left" | Comodo Essential SSL Wildcard || style="text-align:left" | Sectigo Essential SSL Wildcard || style="text-align:left" | COMODO_ESSENTIALSSL_WILDCARD | ||
| + | |} | ||
= FAQs = | = FAQs = | ||
| Line 21: | Line 53: | ||
A: No. Legacy Comodo product names will be backwards compatible so all existing API implementation will work the same as it did before. | A: No. Legacy Comodo product names will be backwards compatible so all existing API implementation will work the same as it did before. | ||
| + | <br><br> | ||
| − | + | You can also visit [[https://sectigo.com/sectigo-story-faq Sectigo’s FAQ]] for a helpful overview. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Latest revision as of 21:35, 23 January 2019
Comodo's CA was acquired by Francisco Partners in late 2017. With this new partnership, Comodo is expanding beyond SSL and has demonstrate a renewed commitment to innovation, digital transformation and service. As a result of this, they have rebranded Comodo to Sectigo!
Following the rebranding, product name changes will be effective starting January 2019. You'll soon start seeing certificates issued by Sectigo instead of Comodo over time. However, this change will happen gradually and seamlessly. It will not affect existing products and Comodo Authority roots will remain trusted.
You can see a list of product name changes in the following section below.
[edit] Product Name Changes
The product name change will be reflected on HEXONET's website and Control Panel. However, this does not affect existing API implementation or price relations.
| Original Name | New Name | Still using the same class name |
|---|---|---|
| Comodo SSL | Sectigo DV SSL | COMODO_SSL |
| Comodo EV SSL | Sectigo EV SSL | COMODO_SSL_EV |
| Comodo SSL Wildcard | Sectigo DV SSL Widcard | COMODO_SSL_WILDCARD |
| Comodo Instant SSL | Sectigo Instant SSL | COMODO_INSTANTSSL |
| Comodo Instant SSL Premium | Sectigo Instant SSL Premium | COMODO_INSTANTSSL_PREMIUM |
| Comodo Premium SSL Wildcard | Sectigo Premium SSL Wildcard | COMODO_PREMIUMSSL_WILDCARD |
| Comodo Positive SSL | Sectigo Positive SSL | COMODO_POSITIVESSL |
| Comodo Essential SSL | Sectigo Essential SSL | COMODO_ESSENTIALSSL |
| Comodo Essential SSL Wildcard | Sectigo Essential SSL Wildcard | COMODO_ESSENTIALSSL_WILDCARD |
[edit] FAQs
Q: What will change within HEXONET?
A: All references to Comodo will be removed and replaced with Sectigo. The product names for SSL certificates will be changed as well.
Q: Do I need to reinstall my SSL certificate with the rebranding?
A: No. All existing Comodo products will not be affected by the new change.
Q: Will existing SSL certificates continue to be trusted?
A: Yes. The rebranding does not impact existing products.
Q: Do I need to make changes to my API implementation?
A: No. Legacy Comodo product names will be backwards compatible so all existing API implementation will work the same as it did before.
