A free ACME authority — the default of the acme.sh client — whose certificates Sectigo issues under ZeroSSL’s name. A CAA record naming zerossl.com does not let it issue: its value is sectigo.com.
| Run by | ZeroSSL GmbH, Austria (HID Global); certificates issued by Sectigo |
| CAA value | sectigo.com — it also accepts usertrust., trust-provider., comodoca., comodo., entrust., affirmtrust. |
| CAA parameters | None documented |
| ACME | https://acme.zerossl.com/v2/DV90 — with an External Account Binding key from your account |
| Cost | Free: unlimited 90-day certificates through ACME; paid plans in its dashboard |
| Certificates | DV only; wildcards, but not together with other names in one certificate |
| Longest certificate | 90 days through ACME; up to 200 days in its dashboard, where a one-year “Annual Certificate” is now several certificates in turn |
| Issuer names on its certificates | ZeroSSL RSA DV SSL CA 2, ZeroSSL ECC DV SSL CA 2, ZeroSSL RSA Domain Secure Site CA |
May ZeroSSL issue for your domain?
Enter a domain or hostname: we read its CAA records as ZeroSSL 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 ZeroSSL
Published on your domain, this lets ZeroSSL 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 "sectigo.com"
An issue record covers wildcard certificates too. To let ZeroSSL 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 "sectigo.com"
example.com. CAA 0 iodef "mailto:security@example.com"
How it reads CAA
Its CAA list is Sectigo’s, because Sectigo issues its certificates: sectigo.com, with the others Sectigo accepts. ZeroSSL’s own help page says to add sectigo.com.
Getting a certificate
With an ACME client and an external account key from the ZeroSSL dashboard’s developer section; the number of keys per user per day is limited.
What changed
- January 2024 — HID Global (ASSA ABLOY) bought ZeroSSL.
- 14 October 2025 — Stopped including TLS client authentication in new certificates.
- 15 March 2026 — Certificates capped at 200 days; a year’s certificate became an Annual Certificate, issued in turns.
- 1 April 2026 — New server-only intermediates, ZeroSSL RSA DV SSL CA 2 and ECC DV SSL CA 2, under Sectigo’s R46 and E46 roots.
Worth knowing
- acme.sh uses ZeroSSL unless told otherwise, so a server set up with it may be on ZeroSSL without anyone choosing it.
- Its certificates name ZeroSSL as issuer; its revocation is by OCSP, with no CRL.
Questions
Why does my CAA record with zerossl.com fail?
Because ZeroSSL is not the issuing authority — Sectigo is — and zerossl.com is not a value Sectigo recognises. Publish 0 issue “sectigo.com” instead.
Sources
Checked on 27 September 2026 against these official sources:
- Invalid CAA Records — help.zerossl.com
- ACME Documentation — zerossl.com
- TLS Combined CP CPS v6.2.5 — sectigo.com
- SSL TLS Certificate Validity Changes New 200 Day Limit Explained — help.zerossl.com