Certificate authorities
For publicly trusted certificates, Cloudflare partners with different certificate authorities (CAs). Refer to this page to check what CAs are used for each Cloudflare offering and for more details about the CAs features, limitations, and browser compatibility.
| Certificate | Algorithm | Let's Encrypt | Google Trust Services | SSL.com | Sectigo | DigiCert |
|---|---|---|---|---|---|---|
| Universal | ECDSA RSA (Paid plans only) | ✅ ✅ | ✅ ✅ | ❌ ❌ | N/A N/A | ✅ Deprecating soon ✅ Deprecating soon |
| Advanced | ECDSA RSA | ✅ ✅ | ✅ ✅ | ✅ ✅ | N/A N/A | ✅ Deprecating soon ✅ Deprecating soon |
| Total TLS | ECDSA RSA | ✅ ✅ | ✅ ✅ | ✅ ✅ | N/A N/A | ❌ ❌ |
| SSL for SaaS | ECDSA RSA | ✅ ✅ | ✅ ✅ | ✅ ✅ | N/A N/A | ✅ Deprecating soon ✅ Deprecating soon |
| Backup | ECDSA RSA | ✅ ✅ | ✅ ✅ | ✅ ✅ | ✅ ✅ | ❌ ❌ |
- Supports validity periods of 90 days.
- DCV tokens are valid for 7 days.
- Hostname on certificate can contain up to 10 levels of subdomains.
- Duplicate certificate limit of 5 certificates ↗ per week.
The main determining factor for whether a platform can validate Let's Encrypt certificates is whether that platform trusts the self-signed ISRG Root X1 certificate. As Let's Encrypt announced a change in its chain of trust in 2024 ↗, older devices (for example Android 7.0 and earlier) that only trust the cross-signed version of the ISRG Root X1 are no longer compatible.
You can find the full list of supported clients in the Let's Encrypt documentation ↗. Older versions of Android and Java clients might not be compatible with Let's Encrypt certificates.
Let's Encrypt Root CAs ↗: For checking compatibility between chain and client. As explained in Certificate pinning, you should not use this list for pinning against.
- Supports validity periods of 14, 30, and 90 days.
- DCV tokens are valid for 14 days.
- Punycode domains are not yet supported.
By cross-signing with a GlobalSign root CA ↗ that has been installed in client devices for more than 20 years, Google Trust Services can ensure optimal support across a wide range of devices.
Currently trusted by Microsoft, Mozilla, Safari, Cisco, Oracle Java, and Qihoo’s 360 browser, all browsers or operating systems that depend on these root programs are covered.
You can use the root CAs list ↗ for checking compatibility between chain and client but, as explained in Certificate pinning, you should not use this list for pinning against.
- Supports validity periods of 14, 30, and 90 days. Enterprise customers using advanced certificates can also choose a validity period of one year.
- DCV tokens are valid for 14 days.
SSL.com DCV tokens are specific for RSA certificates and ECDSA certificates. This means that, for cases where you have to manually perform DCV, you will have to place two validation tokens per certificate order. To avoid management overhead, consider using a full setup, or setting up Delegated DCV.
SSL.com is highly compatible, being accepted by over 99.9% of browsers, tablets, and mobile devices.
SSL.com certificates are cross-signed with Certum ↗ and the CA that cross-signs intermediates ↗ is from 2004.
Acceptable top level domains (TLDs) and current restrictions ↗
- Only used for Backup certificates.
- Backup certificates are valid for 90 days.
Refer to Sectigo documentation ↗.
- Supports validity periods of 14, 30, and 90 days.
- DCV tokens are valid for 30 days.
Due to sanctions imposed by the United States, DigiCert is legally prohibited or restricted from offering its products and services to specific countries or regions. Refer to Embargoed countries and regions ↗ for details.
Refer to DigiCert documentation ↗.
DigiCert Root CAs ↗: For checking compatibility between chain and client. As explained in Certificate pinning, you should not use this list for pinning against.
A Certificate Authority Authorization (CAA) DNS record specifies which certificate authorities (CAs) are allowed to issue certificates for a domain. This record reduces the chance of unauthorized certificate issuance and promotes standardization across your organization.
If you are using Cloudflare as your DNS provider, then the CAA records will be added on your behalf. If you need to add CAA records, refer to Add CAA records.
The following table lists the CAA record content for each CA:
| Certificate authority | CAA record content |
|---|---|
| Let's Encrypt | letsencrypt.org |
| Google Trust Services | pki.goog; cansignhttpexchanges=yes |
| SSL.com | ssl.com |
| Sectigo | sectigo.com |
| DigiCert | digicert.com; cansignhttpexchanges=yes |