Filtering by: domains x clear

We updated the behavior for products that can use wildcard domain names and fully qualified domain names (FQDNs) in a certificate. After August 23, 2021 certificates including the wildcard domain name will only secure the FQDN and all of its same-level domain names without charge.

Subject Alternative Names (SANs) that are not at the same level as the wildcard domain name will be considered additional to the wildcard coverage. For example, a wildcard certificate for * will only allow FQDNs like,, and to be included as SANs in the certificate without charge.


CertCentral Services API: New subaccount endpoints

To make it easier to manage your subaccounts, we added two new endpoints to the CertCentral Services API: List subaccount domains and List subaccount organizations.


Legacy account upgrades 2.0

We are happy to announce that validated domains and active, public SSL/TLS certificates are now included in the data migration when upgrading your legacy console to CertCentral. See What you need to know about account data migration.

With this release, we start a phased upgrade of our legacy consoles to CertCentral. Upgrade criteria is dependent on company size, currency preference, and feature usage.

Note: CertCentral upgrades are free. If you are interested in upgrading now, please contact your account manager or our Support team.

If your legacy account meets the phase one criteria, when you sign in to your console, you'll see an option to upgrade to CertCentral. Upon upgrade, we migrate your organizations and and validated domains to your CertCentral account. Then, when ready, you can import your active, public SSL/TLS certificates.

For more information about the upgrade to CertCentral and data migration, see our Upgrade to CertCentral guide.

Other types of certificates

Private SSL, code signing, S/Mime and other types of certificates cannot be imported at this time. Private SSL/TLS and non-SSL/TLS certificate will be part of a separate migration effort.