Guides CAA

What is CAA?

Your host arranges your website’s certificate. CAA specifies which issuer is authorized. Start with that service and use the right setting.

For a secure connection to example.com, the browser checks that the server belongs to that domain name. Your host arranges a certificate for this check: digital proof issued for the domain. A DNS setting called CAA lets you specify which certificate issuer is authorized.

Check CAA on your own domain

What happens for example.com?

Suppose your host requests the certificate for example.com and renews it automatically. Before issuing a new certificate, the issuer checks the authorization you published in DNS. If the setting names only that issuer, it does not authorize a different issuer.

You usually do not need to choose an issuer yourself: start with the service managing your website’s certificate. Ask which CAA value it needs. A wrong value can block the next issuance or renewal. The setting does not revoke a certificate you already have.

Use the setting from your certificate service

Ask your host for the exact record name and value. A DNS panel with separate fields will usually use the following for this example:

  • Name or Host: example.com, often entered as @ or a blank field.
  • Type: CAA.
  • Flags: 0, unless the documented instructions specify otherwise.
  • Tag: issue, the authorization for ordinary certificates.
  • Value: the issuer name supplied by your certificate service.

Always use the intended DNS name. CAA can also be set for another name or a subdomain. The issuer name is not necessarily the company name displayed in a certificate. Do not paste an entire record line into just the value field. Follow the provider’s instructions for quotation marks or panels with one complete data field.

Reading a complete record line

A complete record line looks like this: example.com. CAA 0 issue "ca1.example.net". This fictional example authorizes the issuer with CAA name ca1.example.net to issue ordinary certificates for example.com. The value identifies an issuer. It is not an address for visitors to your website. Do not copy this fictional value. Use the real value supplied by your certificate service.

Documentation also calls certificate issuers CAs. If you use several certificate services, such as a CDN alongside your host, list their issuers. You can add a second issue record for the second issuer you need. Both authorizations then count. Include automatic renewal and backup issuers in that inventory.

Setting up and checking

  • List every service that requests certificates, including automatic renewal.
  • Copy their documented CAA names and any necessary parameters.
  • After publication, check every name on the certificate request, such as example.com and www.example.com. Allow for old DNS caches.
  • Check whether the queried DNS services return the same settings and at which name the records were found. Technical details call that name the owner.
  • Have the certificate service check in good time that a request or renewal succeeds with these settings. Do not wait until the existing certificate is about to expire.

What a scan result means

DNS Radar compares CAA answers from public DNS services, which may use cached data. The scan does not query the nameservers directly or perform a certificate issuer’s complete checks. An AD flag is the DNS service’s report of successful DNSSEC validation. DNS Radar does not verify the signatures itself.

A favourable result therefore shows what the sampled DNS answers publish, not that a certificate will be issued. The CA must still assess the request, identity and any parameters. The email result is a hypothetical RFC 9495 question for an address at the scanned domain. No actual S/MIME request was examined. For iodef, the scan checks the reporting address’s syntax and form, not whether it is reachable or receives reports.

Which records apply to a request?

The CA starts its CAA query at the requested name. The query also follows DNS aliases such as CNAME. If a query returns no CAA, the CA continues at the parent name under the standard’s lookup rules, up to and including the TLD. The first group of CAA records found at one name is the relevant record set, or RRset. A group on a subdomain replaces the parent’s group. The rules are not combined.

An apex/www difference therefore matters. Suppose example.com authorizes only ca1.example.net. www.example.com is a CNAME to a CDN target where CAA authorizing ca2.example.org is found. Authorization for example.com does not automatically authorize www.example.com. Check the CAA records actually selected for both names. A certificate covering several domain names must satisfy the rules for every name.

If no relevant record set exists, CAA does not restrict issuance. Where restrictions apply to the request, the issuer normally has to satisfy them. Request validation and any documented exceptions in the issuer’s certificate policy or practice statement (CP/CPS) also affect the decision.

Tags for ordinary, wildcard and email certificates

  • issue: which issuers may issue ordinary certificates. It also governs wildcards when issuewild is absent.
  • issuewild: which issuers may issue wildcard certificates, such as for *.example.com. When present, it replaces issue rules for wildcard requests.
  • issuemail: which issuers may issue certificates for email addresses, such as S/MIME. This policy is independent of issue and issuewild.
  • iodef: an address to which an issuer may send reports. Publication alone does not prove that reports are sent or received.

Add issuewild only when wildcard policy should differ. Use issuemail only when you need a separate email-certificate policy.

Some common combinations, without additional conditions:

  • Only iodef: there is a reporting address, but no restriction on issuers of ordinary or wildcard certificates.
  • Only issuewild: wildcard issuance is restricted. Ordinary certificates are not restricted by it.
  • Only 0 issue ";": no issuer is authorized for ordinary certificates, or for wildcards while issuewild is absent.
  • 0 issue ";" alongside 0 issue "ca1.example.net": ca1.example.net is authorized. An empty issuer does not override another authorization.

Watch inheritance: adding only iodef at a subdomain creates its own record set, replacing the parent’s CAA. A restriction on issuers set at the parent no longer automatically applies to that subdomain.

Extra conditions and the critical flag

Ordinary CAA settings usually use flag 0. Flag 128 makes a tag critical: an issuer must understand the tag before it may issue a certificate. This also applies to officially registered tags. Use that flag only when every issuer you need demonstrably supports the tag.

For restrictions to an account or validation method, RFC 8657 defines accounturi and validationmethods parameters on issue and issuewild. They work as intended only with a CA that supports and recognizes them. A syntactically valid value does not prove that support. Copy such values exactly from the CA’s documentation. Parameters on issuemail are CA-specific.

Primary sources

Frequently asked questions

Does CAA revoke existing certificates?

No. CAA is evaluated for new issuance and renewal. Existing certificates remain valid until they expire or are revoked by another mechanism.

What if I use several CAs?

Add a separate issue record for each issuer you need. Include issuers used by hosting, CDNs and automatic renewal. With separate wildcard or email policy, check that the corresponding tags name the right issuers. Authorizations within a tag are additive.

How do ordinary, wildcard and email rules interact?

issue governs ordinary certificates and is the wildcard fallback when issuewild is absent. issuemail is independent and never falls back to either TLS tag.

Does a green scan guarantee issuance?

No. The result describes the sampled DNS publication. The issuer assesses the request and support for any extra conditions itself. Also check certificate renewal with your host or certificate service.

Check CAA on your own domain →