CAA records: why your certificate won't issue (and how to fix it)

A CAA record tells certificate authorities which of them may issue for your domain. Learn the syntax, how to debug CAA failures from Let's Encrypt and others, and how to fix them.

· 6 min read · By the Spot Downtime team

You request a certificate and the authority refuses with something like CAA record for example.com prevents issuance. Nothing is wrong with your server or your validation. A DNS record you (or someone before you) added says that this particular certificate authority is not allowed to issue for the domain.

That record is a CAA (Certification Authority Authorization) record. It is a small safety feature that becomes a confusing blocker the moment you switch certificate providers.

What a CAA record does

Before issuing a certificate, a public certificate authority (CA) must look up the CAA records for the domain and check that it is listed. If CAA records exist and the CA is not in them, it must refuse. If no CAA records exist at all, any CA may issue.

The CA checks the exact name first, then walks up the parents. A CAA record on example.com also applies to www.example.com and api.example.com unless those names have their own CAA records, which then take over.

The syntax

A CAA record has three parts: a flag (almost always 0), a tag, and a value.

example.com.  3600  IN  CAA  0 issue "letsencrypt.org"
example.com.  3600  IN  CAA  0 issuewild "letsencrypt.org"
example.com.  3600  IN  CAA  0 iodef "mailto:[email protected]"
  • issue: the CA may issue certificates for this name. This covers normal and wildcard certificates unless an issuewild record exists.
  • issuewild: rules for wildcard certificates only. If present, it overrides issue for wildcards.
  • iodef: where a CA should report a refused or suspicious request. Optional.

The value is the CA's identifier, usually its domain. Use exactly what the CA documents. Common ones include letsencrypt.org, digicert.com, sectigo.com, pki.goog (Google Trust Services) and amazon.com (AWS Certificate Manager). Check the CA's own documentation before relying on this list from memory.

To forbid all issuance, use an empty value: 0 issue ";".

Why issuance fails

1. You switched certificate providers

The classic case. The domain has a CAA record for the old CA from years ago. You move to Let's Encrypt, or enable a certificate from your CDN or cloud provider, and the new CA is not listed. Add it, keep the old one if you still use it.

2. A platform issues certificates on your behalf

Hosting platforms, CDNs and load balancers often get certificates from a CA you never chose. If issuance or renewal fails only on that platform, look at its docs for which CA it uses and add that CA to your CAA records.

3. Wildcards are blocked separately

An issuewild record that names a different CA, or ";", blocks wildcard certificates even when issue allows the CA. A wildcard request fails while a single-name request for the same CA works.

4. The record sits on the wrong name

A CAA record on a subdomain overrides the parent for that subdomain. If shop.example.com has its own CAA record listing only one CA, adding another CA at example.com does nothing for shop.

5. DNS provider quirks

Some DNS providers don't support CAA as a record type, or mangle the quotes. Others add the quotes for you, and a doubled pair makes the value invalid. Look at what is actually published, not what the dashboard shows.

CAA lookups can also fail because of a broken authoritative DNS server. If the servers return SERVFAIL for the CAA query instead of an empty answer, some CAs treat that as a reason to refuse. A DNS provider that handles unknown record types badly is the usual cause.

How to check what is published

bash
dig +short CAA example.com
# 0 issue "letsencrypt.org"
# 0 issuewild "letsencrypt.org"

# Ask a specific resolver, and check a subdomain
dig +short CAA www.example.com @1.1.1.1

# Ask the authoritative server directly to rule out caching
dig +short CAA example.com @ns1.your-dns-provider.com

An empty answer on the exact name means "look at the parent", so run the query on each level until you find records. If the answer lists CAs but not yours, that is the problem.

Fixing it

  1. Find which CA is refusing, from the error message or the platform's docs.
  2. Look up the identifier that CA documents for CAA.
  3. Add an issue record for it (and issuewild if you need wildcards) at the right name. Keep existing records you still need.
  4. Wait for the old record's TTL to expire if resolvers cached it, then retry issuance.
example.com.  3600  IN  CAA  0 issue "letsencrypt.org"
example.com.  3600  IN  CAA  0 issue "pki.goog"
example.com.  3600  IN  CAA  0 issuewild "letsencrypt.org"

Don't delete everything

Removing all CAA records is the quickest way to unblock issuance, but it also removes the protection. Prefer listing exactly the CAs you use.

Should you use CAA at all?

It is cheap and worthwhile. CAA limits which CAs can be tricked or misconfigured into issuing for your domain. The cost is that every provider change needs a DNS change first, so add CAA updates to your migration checklist.

Catch it before the certificate expires

The danger of CAA is that it fails quietly at renewal time. A certificate issued months ago keeps working until it expires, then the automatic renewal is refused and the site goes down with an expired certificate. If renewals are failing, see why Let's Encrypt renewal fails. To get warned weeks ahead, monitor the certificate's expiry date: how to monitor SSL and domain expiry.

SSL checkerCheck a site's certificate, issuer and expiry date.

Get new guides by email

Practical posts on monitoring, outages, error fixes and on-call, when they're published. No spam.

Unsubscribe from any email with one click. See our privacy policy.

Keep reading