CAA record: what it is and how to check it
Restricts which certificate authorities are allowed to issue TLS certificates for a domain.
What it is
A CAA record (Certification Authority Authorization) lets a domain owner state which certificate authorities (CAs) are allowed to issue TLS certificates for the domain. TLS certificates are what make the padlock and https:// work. Without CAA, any of the dozens of publicly trusted CAs may issue a certificate for any domain, as long as it validates control of that domain.
CAA is defined in RFC 8659, which replaced the original RFC 6844. Since September 2017 every publicly trusted CA must check CAA before issuing.
How it works
When a CA receives a request for a certificate for www.example.com:
- It looks up CAA records for
www.example.com. - If there are none, it looks at the parent,
example.com, and continues up the tree until it finds a CAA record set or reaches the top-level domain. - If it finds no CAA anywhere, issuance is allowed.
- If it finds a CAA set, it may issue only if one of the
issue(or, for wildcard certificates,issuewild) entries names that CA.
If the name is a CNAME, the CA follows the alias and checks CAA at the target as well.
CAA does not revoke certificates that already exist, and browsers do not check it. It is a rule for the CAs at issuance time.
Syntax and fields
A CAA record has three parts after the type:
| Field | Example | Meaning |
|---|---|---|
| Flags | 0 |
0 normally. 128 marks the tag as critical: a CA that does not understand the tag must refuse to issue. |
| Tag | issue |
What the entry controls. |
| Value | "ca.example.net" |
A quoted string, interpreted according to the tag. |
The standard tags are:
| Tag | Meaning |
|---|---|
issue |
The CA named in the value may issue certificates of any kind for this name. |
issuewild |
The CA may issue wildcard certificates (*.example.com). If present, it overrides issue for wildcards. |
iodef |
Where a CA may report a refused request: a mailto: or https: URL. Support varies between CAs. |
The value of issue and issuewild is the CA’s identifying domain, optionally followed by parameters separated by ; (for example, some CAs accept accounturi= to tie issuance to one account). An empty value, ";", means no CA may issue.
Examples
Allow a single CA for all certificates:
example.com. 3600 IN CAA 0 issue "ca.example.net"
Allow two CAs, but wildcard certificates only from the first:
example.com. 3600 IN CAA 0 issue "ca.example.net"
example.com. 3600 IN CAA 0 issue "pki.example.org"
example.com. 3600 IN CAA 0 issuewild "ca.example.net"
Forbid wildcard certificates entirely and ask for reports:
example.com. 3600 IN CAA 0 issue "ca.example.net"
example.com. 3600 IN CAA 0 issuewild ";"
example.com. 3600 IN CAA 0 iodef "mailto:security@example.com"
A domain that should never have any certificate:
parked.example.com. 3600 IN CAA 0 issue ";"
In these examples ca.example.net and pki.example.org stand for your CA’s real identifier, which you find in its documentation.
Planning a CAA rollout
- List the certificates you have. Certificate Transparency logs record every publicly trusted certificate, so a CT search for your domain shows which CAs have issued for it recently.
- Ask your providers. CDNs, hosting platforms and SaaS tools that serve your subdomains may obtain certificates on your behalf. Check which CA identifiers they need.
- Publish CAA at the apex naming those CAs, and add
issuewildonly if you use wildcard certificates. - Watch the next renewals. If one fails with a CAA error, the CA’s message names the record set it found.
Common mistakes
- Forgetting a CA you already use. Your CDN, hosting platform or email provider may obtain certificates for you from a CA you never chose directly. Add CAA and their next renewal fails. List every CA in use before publishing CAA.
- Typos in the CA identifier. The value must match the CA’s documented identifier exactly. A misspelt value silently blocks every CA.
- Setting only
issuewild.issuewildalone does not restrict non-wildcard certificates. Add anissueentry too. - Subdomain records overriding the apex unexpectedly. A CAA set on
shop.example.comreplaces, not extends, the one onexample.comfor that subdomain. - DNS errors during issuance. If your nameservers return
SERVFAILor time out for CAA queries, CAs must refuse to issue. Old or misconfigured DNS servers that mishandle unknown record types can break renewals even if you have no CAA at all. - Using the critical flag without need. Flag
128on an unrecognised tag stops all issuance. Use0unless you know you need it.
How to check it
Use the DNS lookup tool with type CAA. If the exact name has no records, look up its parent too, since CAs climb the tree. The “all records” view of the lookup tool includes CAA alongside the other main record types, which is handy before ordering a new certificate.
Related records
- TXT: another policy record; some CAs use TXT records for domain validation.
- CNAME: CAs follow aliases when checking CAA.
- HTTPS / SVCB: another record that affects how browsers connect securely.
Frequently asked questions
Is a CAA record required?
No. If a domain has no CAA records, any publicly trusted certificate authority may issue for it. Adding CAA records is a simple way to reduce the risk of a certificate being issued by a CA you do not use.
Do browsers check CAA records?
No. CAA is checked by certificate authorities at the moment they issue a certificate, as required by the CA/Browser Forum Baseline Requirements. Browsers do not look at CAA when visiting a site, and existing certificates keep working if you change CAA later.
My subdomain has no CAA record. Which policy applies?
The CA climbs the tree: it checks the exact name, then its parent, and so on, and uses the first CAA record set it finds (RFC 8659). So a CAA record on example.com also covers www.example.com, unless www has its own CAA records.
What value do I use for my certificate authority?
Each CA publishes its CAA identifier, which is usually its main domain name. Check the CA's documentation and use exactly that value; a typo blocks issuance.