The largest commercial authority, selling under DigiCert, GeoTrust, RapidSSL, Thawte and Encryption Everywhere — and the authority behind Azure’s free and managed certificates. digicert.com lets every one of its brands issue.
| Run by | DigiCert, Inc., United States |
| CAA value | digicert.com — it also accepts www., digicert., cybertrust., thawte., geotrust., rapidssl., symantec., digitalcertvalidation., volusion., stratossl., intermediatecertificate., 1and1., quovadisglobal., pkioverheid., amazon., amazontrust., awstrust., amazonaws. |
| CAA parameters | account= (its own domain locking); accounturi and validationmethods only from 15 March 2027 |
| ACME | https://one.digicert.com/mpki/api/v1/acme/v2/directory — with an External Account Binding key from your account |
| Cost | Paid |
| Certificates | DV, OV and EV; wildcards for DV and OV |
| Longest certificate | 200 days — the most any authority may issue since 15 March 2026 |
| Issuer names on its certificates | DigiCert Global G2 TLS RSA SHA256 2020 CA1, DigiCert G5 TLS RSA4096 SHA384 2021 CA1, GeoTrust TLS RSA CA G1, RapidSSL TLS RSA CA G1, Thawte TLS RSA CA G1, Encryption Everywhere DV TLS CA - G2 |
| Also sold as | GeoTrust, RapidSSL, Thawte, Encryption Everywhere, QuoVadis |
| Issues for | Azure — App Service, Front Door, Container Apps and its other managed certificates; Akamai’s OV and EV certificates |
May DigiCert issue for your domain?
Enter a domain or hostname: we read its CAA records as DigiCert 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 DigiCert
Published on your domain, this lets DigiCert 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 "digicert.com"
An issue record covers wildcard certificates too. To let DigiCert 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 "digicert.com"
example.com. CAA 0 iodef "mailto:security@example.com"
To let only your own CertCentral account order certificates for the domain — DigiCert’s domain locking — add the verification token from the account’s domain settings:
example.com. CAA 0 issue "digicert.com; account=YOUR-TOKEN"
How it reads CAA
Every value in its list is equivalent: digicert.com, geotrust.com, rapidssl.com or thawte.com each lets every DigiCert brand issue. It processes issue and issuewild; it does not document iodef.
The list includes Amazon’s four names — amazon.com, amazontrust.com, awstrust.com, amazonaws.com — and DigiCert operates some of Amazon’s older intermediates. A record naming Amazon lets DigiCert issue too.
Getting a certificate
Through CertCentral, or ACME with an external account key from it (the old acme.digicert.com endpoint closed on 24 February 2026). ACME covers DV, OV and EV.
When a CAA record stops it
CertCentral reports caa_check_failed (or caa_not_found, invalid_caa_entry, dns_lookup_timeout_caa) with the message “CAA check failed. Make sure the CAA resource records for the domain are configured correctly.”
What changed
- July 2024 — Revoked 83,267 certificates within days, after finding that one domain-validation path had accepted CNAME records without the required underscore.
- 24 February 2026 — Retired its old ACME endpoint.
- 15 April 2026 — Chrome and Mozilla removed its oldest roots: DigiCert Global Root CA, High Assurance EV Root CA and Assured ID Root CA.
- 15 October 2026 — Issues from its G5 roots by default, for every brand.
- 15 September 2027 — Chrome will keep only DigiCert’s two G5 roots.
Worth knowing
- Azure tells customers to publish 0 issue “digicert.com”, not microsoft.com: Microsoft’s own value covers only its first-party certificates.
- It does not honour accounturi or validationmethods yet; it will by 15 March 2027, when every authority must.
- symantec.com still works: DigiCert took over Symantec’s certificate business, which Chrome distrusted in 2017–18.
Questions
Which CAA value do I need for GeoTrust, RapidSSL or Thawte?
Any of DigiCert’s values — digicert.com is the usual one. Each lets every DigiCert brand issue; geotrust.com, rapidssl.com and thawte.com work as well.
What CAA record does Azure need?
0 issue “digicert.com”. Azure’s free App Service certificates, Front Door and Container Apps certificates are all issued by DigiCert, and fail to issue or renew without it once the domain has CAA records.
Sources
Checked on 27 September 2026 against these official sources:
- Digicert public trust cp cps v7 09 — digicert.com
- DNS CAA resource record check — docs.digicert.com
- DigiCert’s Root Strategy: Aligning with New Industry Standards — knowledge.digicert.com
- Install a TLS/SSL Certificate for Your App — learn.microsoft.com