Skip to content

Scan your domain with 35 DNS and email security checks at zerohook.org.

What is / Full version

CAA

CAA tells a public CA which issuers may mint a certificate for the name. It is not a check a TLS client runs on a presented certificate.

Short answerAll topics in What is

Before issuance

Before issuing a certificate, a compliant CA must check for a Relevant RRset. If that set exists, the CA must not issue unless the request is consistent with it, or an exception in the CA's CP or CPS applies.

Relying Parties must not use CAA records as part of certificate validation. A certificate that does not match today's CAA may still have matched the CAA that was published when it was issued.

issue and issuewild

RFC 8659's example that authorises two CAs is certs.example.com CAA 0 issue "ca1.example.net" and CAA 0 issue "ca2.example.org". issue ";" grants no issuer.

issuewild has the same syntax as issue but only for a wildcard name. If any issuewild is present for that wildcard request, every issue property is ignored for that request.

Relevant RRset

A public CA has to check CAA before it issues. A relying party must not use CAA as part of certificate validation. The issue, issuewild, and iodef tags live in that RFC. DNSSEC signs the zone. DANE publishes TLSA. Neither of those is this record.

issuewild and iodef

issue, issuewild, and iodef are the tags in RFC 8659, November 2019. issue ";" is how that RFC shows a name that grants no issuer. A relying party must not use CAA as part of certificate validation. DNSSEC and DANE are different records.