CAA Records

Table of Contents

What is a CAA record?

A Certification Authority Authorization (CAA) record is used to specify which certificate authorities (CAs) are allowed to issue certificates for a domain.

The purpose of the CAA record is to allow domain owners to declare which certificate authorities are allowed to issue a certificate for a domain. They also provide a means for indicating notification rules in case someone requests a certificate from a not authorized certificate authority. If no CAA record is present, any CA is allowed to issue a certificate for the domain. If a CAA record is present, only the CAs listed in the record(s) are allowed to issue certificates for that hostname.

CAA records can set policy for the entire domain, or for specific hostnames. CAA records are also inherited by subdomains, therefore a CAA record set on will also apply to any subdomain, such as (unless overridden). CAA records can control the issuance single-name certificates, wildcard certificates, or both.

The DNS CAA record is specified by RFC 6844.

CAA record format

The CAA record is represented by the following elements:

flag An unsigned integer between 0-255.
  It is currently used to represent the critical flag, that has a specific meaning per RFC.
tag An ASCII string that represents the identifier of the property represented by the record.
value The value associated with the tag.

The CAA record consists of a flags byte and a tag-value pair referred to as a property. Multiple properties MAY be associated with the same domain name by publishing multiple CAA RRs at that domain name.

The canonical representation is:

CAA <flags> <tag> <value>

The RFC currently defines 3 available tags:

  • issue: explicity authorizes a single certificate authority to issue a certificate (any type) for the hostname.
  • issuewild: explicity authorizes a single certificate authority to issue a wildcard certificate (and only wildcard) for the hostname.
  • iodef: specifies an URL to which a certificate authority may report policy violations.

CAA record usage

As explained in the format section, each CAA record contain only one tag-value pair. The tag must be one of the currently available tags. For example, if we want to limit the issuance of SSL certificates for to the Let’s Encrypt certificate authority, we should add the following CAA record:  CAA 0 issue ""

If we want to allow both Let’s Encrypt and Comodo, we should add 2 CAA records, one for each CA:  CAA 0 issue ""  CAA 0 issue ""

If we want to allow Let’s Encrypt and Comodo only for wildcard, then we can use the issuewild:  CAA 0 issue ""  CAA 0 issuewild ""

Note that the presence of issuewild will override the issue. Therefore, Let’s Encrypt is not allowed to issue wildcard certificates (regardless of the fact they don’t support this type of certificate).

Finally, to get notified of policy violations you can add a record with the iodef tag, containing the email address to notify:  CAA 0 iodef ""

As mentioned before, the records are inherited by child hostnames. Let’s have a look at an example of subdomain configuration:        CAA 0 issue ""  CAA 0 issue ""   CAA 0 issue ""   CAA 0 issue ""

In the example above, Let’s Encrypt is the default CA for the domain. However, only Comodo can issue a certificate for Both Comodo and Let’s Encrypt can issue certificates for And what about Because no record exists for, but there is a record for, in this case only Let’s Encrypt will be allowed to issue for

Comodo Wildcard Certificates

Customers who purchase a Comodo wildcard certificate from us will need to make sure they have an issue and issuewild CAA record because they add an additional single-name to the certificate to cover the non-wildcard name. For example, buying a certificate for * will issue a certificate with both and * in the certificate names. This means you will need to configure your CAA records like so:  CAA 0 issue ""  CAA 0 issuewild ""

The above rules will apply to subdomain wildcard certificates as well.

Querying CAA records

The CAA record is a relatively new resource record (RR), therefore not all tools already support it. A notable example is dig, that currently doesn’t support the standard syntax for querying CAA records. In order to query the CAA record for a domain with dig you must specify the RR type (257) directly.

$ dig type257

; <<>> DiG 9.8.3-P1 <<>> type257
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64266
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;            IN  TYPE257

;; ANSWER SECTION:     86399   IN  TYPE257 \# 19 0005697373756573796D616E7465632E636F6D

;; Query time: 51 msec
;; WHEN: Thu Dec 29 21:07:18 2016
;; MSG SIZE  rcvd: 59

dig also doesn’t support CAA inheritance, and the output of the query is the binary-encoded record (although in newer versions of dig, support for parsing the record data is present).

In order to test the development of our CAA implementation, at DNSimple we developed a simple utility called dnscaa. It’s a Go package that allows you to fetch CAA records, and it comes with a handy CLI.

$ digcaa

1 records found 86399   IN  CAA 0 issue ""

Manage CAA records

From the DNSimple record editor you can add, remove, and update CAA records.