How to add a CAA record

Publish CAA records naming the certificate authorities you actually use, so no other authority may issue certificates for the domain.

Last reviewed

Why it matters

Without CAA, any publicly trusted certificate authority can issue a certificate for the domain once it has validated control. With CAA, a compliant authority must check the record first and refuse if it is not listed, which narrows who can mis-issue.

How to fix it

Replace the highlighted values: example.com with your domain.

Any DNS host

  1. Find every certificate authority that issues for the domain and its subdomains. A CAA record at the apex also applies to every subdomain without one of its own, so leaving out the authority behind a shop, a blog or a landing-page builder breaks that service's next renewal.

Check the live certificate's issuer:

echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -issuer

Then list every certificate issued for the domain and its subdomains in the past year in the Certificate Transparency logs at crt.sh: search for example.com and for %.example.com.

  1. Match each issuer to its CAA value:
Issuer in the certificate CAA value
Let's Encrypt letsencrypt.org
Google Trust Services pki.goog
Sectigo sectigo.com
DigiCert (also Thawte, GeoTrust, RapidSSL) digicert.com
SSL.com ssl.com
Amazon (AWS Certificate Manager) amazon.com
  1. Add one CAA record per authority at the apex: name @, type CAA, flags 0, tag issue, the authority as the value, TTL 3600. In zone-file form, for a site on Let's Encrypt with one subdomain on Google Trust Services:
example.com.  3600  IN  CAA  0 issue "letsencrypt.org"
example.com.  3600  IN  CAA  0 issue "pki.goog"
  1. Wildcards are covered by issue already. Add an issuewild record only if wildcard certificates must be treated differently: once any issuewild exists, issue no longer applies to wildcards. To forbid wildcards while allowing ordinary certificates:
example.com.  3600  IN  CAA  0 issuewild ";"

Sources: RFC 8659, Let's Encrypt on CAA, Google Trust Services, Sectigo, DigiCert, AWS Certificate Manager.

Cloudflare

  1. Go to DNS > Records > Add record, set Type to CAA, Name to the domain, choose a Tag, enter the authority in CA domain name, and Save. Repeat for each authority.

  2. If the site is proxied through Cloudflare with Universal SSL and Cloudflare is your DNS host, Cloudflare adds CAA records for its own authorities as soon as you add any CAA record. They do not appear in the dashboard. Add records only for the other authorities you use, such as DNS-only subdomains or subdomains hosted elsewhere.

  3. With Advanced certificates, Cloudflare does not add them: add the authority you chose for the advanced certificate yourself.

  4. If Cloudflare is not the authoritative DNS (a CNAME setup, or a subdomain zone whose parent lives elsewhere), add Cloudflare's authorities at the DNS host yourself, using the values on Cloudflare's certificate authorities page:

example.com.  3600  IN  CAA  0 issue "letsencrypt.org"
example.com.  3600  IN  CAA  0 issue "pki.goog; cansignhttpexchanges=yes"
example.com.  3600  IN  CAA  0 issue "ssl.com"
example.com.  3600  IN  CAA  0 issue "sectigo.com"

Cloudflare says its list "is not exhaustive", so check that page again from time to time.

Sources: CAA records, Cloudflare's certificate authorities, troubleshooting CAA.

Check that it worked

dig CAA example.com +short
dig @1.1.1.1 CAA example.com +short

A name that had no CAA record before can stay cached as "no record" for up to the zone's negative TTL, the last number in dig SOA example.com +short. Wait that long, then run the Owl Keeper DNS check again.

Test it now with the free DNS and CAA checker. No account needed.

What can go wrong

  • A forgotten authority breaks renewals, not today's certificates. It shows up weeks later, when a CDN, a site builder on a subdomain, a hosting panel or an MTA-STS host fails to renew. Search crt.sh for subdomains first.
  • A typo blocks all issuance. A malformed issue value is read as ";", which forbids every authority.
  • Adding issuewild for one authority stops the issue records applying to wildcards.
  • CAA follows CNAMEs: a subdomain that is a CNAME takes the CAA record of its target, if it has one.