CAA Record Checker and Generator

Check a domain's CAA records from its own nameservers, see which certificate authorities can issue for it, and generate the records to change that.
  • Enter a domain name to check its CAA records.
  • Public domain names only.
  • Limit: 30 checks per hour per visitor.

CAA record generator

Select the certificate authorities (CAs) allowed to issue certificates for your domain. The records below update as you go and block any CAs you leave out.

You can usually add CAA records to your main domain. Subdomains use those records unless they have their own.

Allowed certificate authorities

Certificate authority Single name Wildcard
Let's Encrypt letsencrypt.org
Actalis actalis.it
AWS Certificate Manager amazon.com
DigiCert digicert.com
GlobalSign globalsign.com
GoDaddy godaddy.com
Google Trust Services pki.goog
Sectigo sectigo.com
SSL.com ssl.com
ZeroSSL sectigo.com
Single name is a certificate for exact names such as www.example.com. Wildcard is one for *.example.com.

Violation reports

Your CAA records

Let's Encrypt can issue certificates for example.com, including wildcards. Other CAs are blocked.

Name Type Flags Tag Value
example.com CAA 0 issue letsencrypt.org

Before you publish, include the CAs used by your CDN, load balancer, hosting platform, and any other service that gets certificates for your domain. Search the Certificate Transparency logs to see which CAs have issued certificates for your domain. To add a CA that isn't listed, copy an issue line and replace its value with that CA's CAA value.

What is a CAA record?

A CAA (Certification Authority Authorization) record is a DNS record that lists the certificate authorities allowed to issue SSL/TLS certificates for a domain. Every public CA must check these records before issuing a certificate and reject the request if it isn't allowed. This check has been required since September 2017.

Publishing one is optional. A domain with no CAA records can get a certificate from any CA, which is how most domains are set up.

example.com.  IN  CAA  0 issue "letsencrypt.org"
  • Flags. Almost always 0. 128 marks the record as critical: a CA that doesn't understand its tag has to refuse to issue.
  • Tag. issue names a CA that can issue any certificate. issuewild names one that can issue wildcards. iodef says where a CA can report a request it refused.
  • Value. The CA's issuer domain, such as letsencrypt.org, or ; for no CA at all.

The format is defined in RFC 8659.

How a CAA lookup works

A CA checks the domain name on the certificate, then its parent domains. For www.shop.example.com it checks www.shop.example.com, then shop.example.com, then example.com, then com. It stops at the first name that has any CAA records and uses only those.

  • The closest records win. Records on a subdomain replace the ones on its parent. They are not added together.
  • CNAMEs are followed. If a name is an alias, the CA reads the CAA records at the name it points to. A subdomain pointed at a CDN or hosting provider can pick up that provider's records this way.
  • Wildcards have their own tag. For *.example.com the CA uses the issuewild records if there are any, and the issue records if there aren't. For every other name, issuewild records are ignored.
  • A failed lookup is a refusal. If the nameservers time out or answer SERVFAIL, the CA has to refuse. That is not the same as finding no records.

The checker above follows these steps and shows each domain it checked. It queries every authoritative nameserver for the zone and flags any conflicting answers.

CAA record values for each certificate authority

The value in a CAA record is a domain name the CA has chosen to identify itself. These are the values for the certificate authorities CertKit issues from.

Certificate authority CAA value Also accepted
Let's Encrypt letsencrypt.org
Actalis actalis.it
AWS Certificate Manager amazon.com amazontrust.com, awstrust.com, amazonaws.com
Any one of the four authorizes AWS.
DigiCert digicert.com www.digicert.com, digicert.ne.jp, cybertrust.ne.jp, thawte.com, geotrust.com, rapidssl.com, symantec.com, digitalcertvalidation.com, quovadisglobal.com, pkioverheid.nl
GlobalSign globalsign.com
GoDaddy godaddy.com starfieldtech.com
Google Trust Services pki.goog
Sectigo sectigo.com trust-provider.com, usertrust.com, comodoca.com, comodo.com, entrust.net, affirmtrust.com
SSL.com ssl.com
ZeroSSL sectigo.com trust-provider.com, usertrust.com, comodoca.com, comodo.com, entrust.net, affirmtrust.com
ZeroSSL certificates are issued by Sectigo, so it uses Sectigo's value.

CAA record examples

Allow one CA

example.com.  IN  CAA  0 issue "letsencrypt.org"

Allow two CAs

A second CA gives you a backup if your primary CA has an outage or loses browser trust. Add it before you need it.

example.com.  IN  CAA  0 issue "letsencrypt.org"
example.com.  IN  CAA  0 issue "pki.goog"

Allow a CA, but no wildcards

example.com.  IN  CAA  0 issue "letsencrypt.org"
example.com.  IN  CAA  0 issuewild ";"

Block new certificates

For a parked domain, or one that should never have a certificate.

example.com.  IN  CAA  0 issue ";"

Allow one ACME account at a CA

Naming a CA lets anyone who can pass validation at that CA get a certificate. RFC 8657 adds parameters that narrow it to one ACME account and one validation method. That is what stops a subdomain takeover from getting a certificate at the same CA you use.

example.com.  IN  CAA  0 issue "letsencrypt.org; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/123456; validationmethods=dns-01"

How to add a CAA record

  1. Check your current records. Run the lookup above. If the domain already has CAA records, start from them.
  2. List everything that gets certificates for the domain. Your own ACME clients, and any CDN, load balancer, or hosting platform that issues certificates for you. The Certificate Transparency log search shows which CAs have issued for the domain.
  3. Generate the records. Pick those CAs in the generator.
  4. Add them at your DNS provider. Most providers have a CAA record type with separate fields for flags, tag, and value. Where there is a single value field, as in Amazon Route 53, enter all three: 0 issue "letsencrypt.org".
  5. Check again. The lookup reads from the authoritative nameservers, so the change shows up as soon as they have it.

Common CAA problems

  • "CAA record for example.com prevents issuance." Let's Encrypt returns this, with the error type urn:ietf:params:acme:error:caa, when the records that apply don't name it. Add the CA's value next to the ones already there. For a wildcard, check the issuewild records too.
  • "SERVFAIL looking up CAA." The nameservers failed to answer the CAA query, often because of a DNSSEC problem or DNS software that doesn't handle the record type. The CA refuses even if the domain has no CAA records at all.
  • A subdomain blocks a CA even though you haven't added CAA records. It is probably a CNAME to a provider whose own CAA records apply. The lookup above shows the alias and where the records came from.
  • A CDN or hosting platform stops renewing. It issues certificates for your domain from a CA your records don't list. Add the CAs it uses.
  • Cloudflare allows CAs you didn't list. On a domain using Cloudflare's Universal SSL, adding any CAA record makes Cloudflare add records for the CAs it issues from, such as letsencrypt.org, pki.goog, ssl.com, and sectigo.com. They don't appear in the Cloudflare dashboard. The lookup above reads the nameservers, so it shows them.

CAA is one of the first things to check when switching certificate authorities.

What CAA records don't do

A CAA record stops the CAs you didn't pick. It doesn't stop someone who controls your DNS, and certificates issued before you published it stay valid. That includes certificates the previous owner of a domain still holds.

CAA also doesn't tell you what has been issued. Certificate Transparency does: every publicly trusted certificate is written to a public log. CertKit's certificate discovery watches those logs for your domains and alerts you when a certificate appears that you weren't expecting.