Your SSL certificate is valid right now, but someone has obtained a certificate for a domain you don't manage, and browsers consider it valid. This is exactly the moment to look at the CAA record. Or the opposite: Let's Encrypt automatic renewal has failed, and all you have in the log is a vague line saying certificate issuance is not permitted. Both cases share the same root cause, and both are solved with a few lines of DNS.
The CAA record is a simple mechanism: you tell every CA that only a certain authority is allowed to issue certificates for this domain. A CA is required to check this record before issuance and reject the request if its name is not on the list. This check has been mandatory for all trusted CAs since 2017 and is standardized in RFC 8659.
CAA Record Syntax and Its Three Tags
The record structure has three parts: a flag, a tag, and a value. In a DNS panel you usually see only three fields: name, tag, and value. A real example for the domain example.com:
example.com. CAA 0 issue "letsencrypt.org"
example.com. CAA 0 issuewild "letsencrypt.org"
example.com. CAA 0 iodef "mailto:security@example.com"
There are three tags, and each does something different:
issue: which CA is allowed to issue regular certificates. The value must be the CA's domain, not its brand name.issuewild: which CA is allowed to issue wildcard certificates. If you don't write this tag, wildcard certificates from any CA allowed byissueare accepted.iodef: an address for receiving violation reports. If a CA receives a request outside your policy, it can notify this address.
A flag of zero means "non-critical." A value of 128 means "critical," and in practice almost nobody uses it, because CAs don't behave consistently with it. Set it to zero and forget about it.
What Is the Correct Value for the issue Tag
This is where most mistakes happen. The value must be the CA's official domain, not its trade name. For Let's Encrypt you write letsencrypt.org, not letsencrypt and not letsencrypt.com. For Sectigo you write sectigo.com. If the name is wrong, the CA doesn't see itself on the list and rejects the request. You won't see any clear error either; issuance just fails.
Second point: if the CA uses an extra parameter, such as 0 issue "letsencrypt.org; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/123456", write these parameters exactly as the CA's documentation says. Let's Encrypt supports accounturi and validationmethods, which means you can restrict issuance to a specific account, not just to a CA.
Why a Wrong CAA Blocks Issuance and How to Diagnose It
When a CA receives a certificate request, it checks the CAA record of the domain and all its parents up to the root. If there is no record at any level, it is allowed. If there is a record and its name is not on the list, it is rejected. This "inheritance from the parent" is the key point many people don't know: if you put a CAA record on example.com, it also affects shop.example.com, unless the subdomain has its own record.
A common error in the ACME log looks something like this:
Error creating new order :: CAA record for shop.example.com prevents
issuance by letsencrypt.org
Or in Certbot:
urn:ietf:params:acme:error:caa :: CAA record for example.com prevents
issuance by letsencrypt.org
To see the actual status, use the command line:
dig CAA example.com +short
dig CAA _acme-challenge.example.com +short
dig CAA shop.example.com +short
If the output is empty, there is no record and the CA is free to issue. If there is output, you need to check whether the value exactly matches the name of the requesting CA. To fully check a domain's records and make sure nothing is missed, a DNS record lookup is faster than guessing.
This Is Where People Go Wrong
The real mistake I've seen many times: someone sets a CAA record with the issue tag and the value "letsencrypt.org", then months later goes to another CA and can't get a new certificate. They don't understand the cause either, because they've forgotten about the CAA record. The sign is this: a certificate request from the second CA is rejected with a CAA error, while the same CA works fine for your other domain. The solution: add every CA you might use in the future to the record from the start, or at least leave a note in the team documentation.
Second mistake: setting a CAA record on the root without paying attention to subdomains. If you restrict example.com to one CA and then want to get a certificate for api.example.com from another CA, you must set a separate CAA record for that subdomain. Otherwise the parent's inheritance will block you.
Restricting Issuance to One Account, Not Just One CA
If you want to be stricter, you can restrict issuance to a specific account at the CA. Let's Encrypt supports this with the accounturi parameter:
example.com. CAA 0 issue "letsencrypt.org; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/123456"
This means that even if someone requests with another account at the same CA, it is rejected. It's worth it for sensitive domains. The cost is that if you change the account or the account number changes, you must update the record too. In practice, most teams forget this, and after migrating to a new account, automatic renewal breaks.
Comparing Options: CAA vs. Other Methods
| Method | What it blocks | Cost and limitation |
|---|---|---|
| CAA record | Certificate issuance by unauthorized CAs | Depends on the CA implementing it correctly; if a CA doesn't follow the standard, it has no effect |
| Certificate Transparency Monitoring | Detecting an issued certificate, not preventing it | Requires a monitoring service and manual review of alerts |
| DNSSEC | Tampering with DNS responses | Operational complexity and a complete chain of trust |
| HSTS | Connections without TLS in the browser | Browser-side only; doesn't prevent certificate issuance |
If you can only do one thing, choose CAA. It's the lowest-cost layer with the greatest deterrent effect. But don't let it be the only layer: also enable CT monitoring so that if one day a CA violates the standard, at least you'll know.
CAA Record and Automatic Renewal: What Breaks Renewal
The most common complaint we receive is: "The automatic certificate doesn't renew and I don't have any clear error." In nine out of ten cases, the CAA record is to blame. Either its value is wrong, or a new CA has been added that isn't in the record, or the record was placed on the parent and has victimized the subdomain.
Set up the check order like this: first dig CAA on the domain and all parents, then check the exact value, then check that your current CA is the one written in the record. If you use Certbot, run certbot renew --dry-run; this command tests the whole path without consuming issuance quota and shows the CAA error right there. If you have other DNS errors too, the DNS troubleshooting guide explains the correct order for checking records.
A practical tip: keep the CAA record's TTL short, say 300 seconds, so that when you change the CA you don't have to wait hours for propagation. The guide to choosing TTL values in DNS tells you what number makes sense for each record type.
When CAA Doesn't Help
The CAA record is a convention, not a technical lock. A CA that doesn't follow the standard can issue a certificate and you have no way to prevent it. Also, if someone gains control of your DNS, they can delete the CAA record and then get a certificate. So CAA doesn't replace controlling access to the DNS panel and enabling two-factor authentication.
Second limitation: some CAs check the CAA record only on the main domain and ignore subdomains. This is a violation, but it happens in practice. If domain security is critical for you, take CT monitoring seriously.
If your domain is hosted on a server where you don't control DNS, you must ask the provider to add the CAA record. For domains hosted on Linux hosting, this is done from the DNS panel and doesn't require support intervention.
Frequently Asked Questions
Can a CAA record completely stop certificate issuance?
Yes, if you set a CAA record with the issue tag and the value ";", you tell all CAs that none are allowed. This mode is useful for retired or migrating domains. But be careful: if you later want to get a certificate, you must first remove this record and wait for the TTL to propagate.
Why didn't my Let's Encrypt certificate renew after adding CAA?
The record value probably doesn't match the CA's official name, or the record was placed on the parent and has restricted the subdomain too. Check with dig CAA on the domain and subdomains and set the value to exactly letsencrypt.org. If you've used the accounturi parameter, check the account number too.
Does CAA affect subdomains too?
Yes. The CA checks the CAA record from the domain toward the root, and the first record it finds is applied. If you set a record on example.com, shop.example.com is also affected, unless you define a separate record for the subdomain.
What's the difference between issue and issuewild?
The issue tag controls regular certificate issuance and issuewild controls wildcard certificate issuance. If you don't write issuewild, the CAs allowed in issue can also issue wildcard certificates. To restrict wildcard separately, write both tags.
Next step: right now, run dig CAA on your main domain and two important subdomains. If the output is empty, add an issue record for your current CA and keep the TTL short. If there is output, make sure the CA you use today is on the list. These two minutes prevent a failed renewal in the middle of the night.