CAA at Cloudflare: what the DNS editor can do
You create the CAA record in the dashboard among the DNS records, with the type CAA, the name, the tag and the certificate authority’s domain name. Each authority gets its own record.
If Universal SSL is active, Cloudflare automatically adds CAA records for its own certificate authorities as soon as the zone has a CAA record. These additional records are not shown in the dashboard; a CAA query of the domain reveals them. As an example the Cloudflare documentation shows records for Let’s Encrypt (letsencrypt.org), Google Trust Services (pki.goog), SSL.com (ssl.com) and Sectigo (sectigo.com), each as issue and issuewild; according to Cloudflare the list can change. For certificates from Advanced Certificate Manager Cloudflare adds nothing; there you enter the chosen authority yourself.
CAA is inherited by subdomains and followed through CNAME targets. A record on the apex domain that excludes Cloudflare’s certificate authorities can therefore also make issuance for subdomains fail.
How to create the CAA record at Cloudflare
The way at Cloudflare:
- In the Cloudflare dashboard open the domain and go to “Records” under “DNS”.
- Choose “Add record” and select “CAA” as the “Type”.
- Enter the name (@ for the apex domain), the tag and the certificate authority’s domain under “CA domain name”.
- Save with “Save”; create a separate record for every further certificate authority.
Click path at Cloudflare
Official guide from Cloudflare: Add CAA records(opens in a new tab)
Structure of the CAA record
A CAA record defines which certificate authorities may issue certificates for the domain. It consists of flag, tag and value: issue allows an authority to issue for the domain, wildcard certificates included, as long as there is no issuewild record. issuewild applies to wildcard certificates only and takes precedence over issue there. iodef names an address for reports. Without a CAA record any authority may issue; as soon as one exists, only those named. So first collect every authority the domain actually uses, including those of the CDN, shop system or mail provider.
The example allows Let’s Encrypt for regular and wildcard certificates. To forbid wildcard certificates altogether, add the line 0 issuewild ";"; to reserve them for another authority, name that one in the issuewild record.
example.com. CAA 0 issue "letsencrypt.org"
example.com. CAA 0 iodef "mailto:security@example.com"Verify and keep an eye on it
The CAA checker below reads the records the way a certificate authority sees them, including inheritance from the apex domain. You see right away whether the record has arrived at Cloudflare and whether the authority of the current certificate remains allowed. DomainWarn keeps checking CAA and certificate afterwards and alerts you when a renewal would fail because of CAA.