A commercial authority and one of the authorities Cloudflare and Shopify use; it issues the certificates named “Cloudflare TLS Issuing CA”. Its CAA value is ssl.com.
| Run by | SSL Corporation, United States |
| CAA value | ssl.com |
| CAA parameters | Not documented |
| ACME | https://acme.ssl.com/sslcom-dv-rsa — with an External Account Binding key from your account |
| Cost | Paid — ACME is a way to receive the certificates you buy |
| Certificates | DV, OV, IV (individual) and EV; wildcards with DNS validation |
| Longest certificate | 198 days, by its own account, since March 2026 |
| Issuer names on its certificates | SSL., SSL., Cloudflare TLS Issuing ECC CA 1–4 |
| Issues for | One of the authorities Cloudflare and Shopify use |
May SSL.com issue for your domain?
Enter a domain or hostname: we read its CAA records as SSL.com must — its own, or the nearest parent’s — and say whether they let it issue, for wildcards too, and which authority issued the certificate it serves now.
The CAA record for SSL.com
Published on your domain, this lets SSL.com issue for it and for every name under it that has no CAA records of its own. Every authority not named must refuse. Keep the records for any other authority you use — your host’s or CDN’s included.
example.com. CAA 0 issue "ssl.com"
An issue record covers wildcard certificates too. To let SSL.com issue wildcards and no one else, add an issuewild record — once there is one, issue records stop counting for wildcards — and an iodef address for authorities to report refused requests to:
example.com. CAA 0 issuewild "ssl.com"
example.com. CAA 0 iodef "mailto:security@example.com"
How it reads CAA
It processes issue, issuewild and iodef, and should send reports to an iodef address (mailto: and https: only). For BIMI mark certificates the tag is issuevmc.
Getting a certificate
ACME directories for RSA and ECDSA DV certificates, with credentials from your SSL.com account; its guide says an external account key is required, though the directories do not ask for one. It sets no ACME rate limits.
What changed
- April 2025 — Mis-issued certificates, including one for aliyun.com, through a faulty email-to-DNS-contact validation method, which it disabled.
- 15 September 2025 — Dropped TLS client authentication.
- 5 November 2025 — Bought VikingCloud’s certificate business (SecureTrust and Trustwave).
- 5 May 2026 — Moved issuance to its 2022 roots.
Worth knowing
- Certificates on Cloudflare-proxied sites can name “Cloudflare TLS Issuing ECC CA 1”: SSL.com issues them, and ssl.com is the value.
- Entrust resold its certificates from August to December 2024 — the “Entrust … TLS Issuing CA 1” intermediates are SSL.com’s.
Questions
Why is ssl.com in my Cloudflare zone’s CAA records?
Cloudflare adds it with Let’s Encrypt, Google Trust Services and Sectigo once the zone has any CAA record: SSL.com is one of the authorities it uses.
Sources
Checked on 27 September 2026 against these official sources:
- SSLcom CP CPS — legal.ssl.com
- Understanding CAA Check Failures and How to Resolve Them — ssl.com
- What SSL’s Root Migration Means for You — ssl.com
- 1961406 — SSL.com: DCV bypass and issue fake certificates for any MX hostname — bugzilla.mozilla.org