ActiScore

MSPs

What Is a CAA Record and Should I Add One? | Complete Guide

Rodney Hall, COO— AI-assisted and reviewed prior to publication.

Photo for: What Is a CAA Record and Should I Add One? | Complete Guide

A CAA record is a DNS record that specifies which certificate authorities are authorized to issue SSL certificates for your domain. If one or more CAA records are present, only the CAs explicitly listed are allowed to issue certificates. Certificate authorities are required to check the CAA record.

How does restricting certificate authorities reduce risk?

Before CAA records existed, any public certificate authority could theoretically issue an SSL certificate for any domain if someone managed to trick their verification process. By publishing a CAA record, you lock this down (dnslookuponline.com). Without a CAA record, any one of hundreds of publicly trusted certificate authorities can issue a certificate for your domain. An attacker who can demonstrate domain control, even temporarily through a DNS hijack, a BGP route leak, or a compromised email address, can obtain a valid, browser-trusted certificate (dnsassistant.com).

CAA helps prevent mis-issuance of certificates, which could otherwise be exploited for malicious activities like phishing or man-in-the-middle attacks. The record acts as an allowlist. If a CA not on your list attempts issuance, a CA not listed in the CAA record must refuse to issue (encryptionconsulting.com).

The protection is limited. CAA is only as strong as CA compliance. A CA that ignores the record, or a CA that is not part of the public WebPKI, is not stopped by it (goranstimac.com). DNS record spoofing is rare, but it remains a potential risk. If an attacker gains access to your DNS, they can remove or modify your CAA record, allowing any CA to issue certificates. Still, for most MSPs managing client domains, the DNSimple documentation confirms it closes a significant gap.

What syntax allows a specific certificate authority?

The basic format is CAA 0 issue "ca-domain.com" where the flag is typically 0, the tag is issue, and the value is the CA's domain in quotes. For example, the flag (0), the tag (issue) and the value ("letsencrypt.org") produces:

CAA 0 issue "letsencrypt.org"

There are three tags: issue (this CA may issue certificates for this domain), issuewild (this CA may issue wildcard certificates), and iodef (where to report a violation attempt).

Adding any issuewild record overrides the issue tag for wildcards specifically. If you need wildcard certificates from Let's Encrypt, add both CAA 0 issue "letsencrypt.org" and CAA 0 issuewild "letsencrypt.org". The issue tag authorizes non-wildcard certificates (and wildcard if no issuewild exists).

You can authorize multiple CAs by adding separate records. CAA records may be set to authorise multiple CAs if the 0 flag is set. For example, if you use both DigiCert and Let's Encrypt:

CAA 0 issue "digicert.com"
CAA 0 issue "letsencrypt.org"

Common CA identifiers include letsencrypt.org, digicert.com, sectigo.com, pki.goog (Google Trust Services), and amazon.com (AWS Certificate Manager). Check ActiScore's pricing (/pricing) for DNS visibility across managed client domains.

How does inheritance affect subdomains?

CAA records at the root domain apply to all subdomains unless a subdomain has its own CAA record. You only need subdomain-specific CAA records if you want different authorization for specific subdomains.

The CA will always respect the CAA record closest to the domain name it is issuing a certificate for. So if you're requesting a cert for "www.community.example.org", the CA will check "www.community.example.org", then "community.example.org", then "example.org", stopping at the first CAA record it finds.

This means a single CAA record at the apex protects the entire hierarchy. A subdomain can have its own CAA rule. The CA always uses the closest record, so a subdomain record replaces the main domain rule for that name only. If api.example.com needs DigiCert but the rest of the domain uses Let's Encrypt, add a subdomain-specific record for api.example.com authorizing DigiCert.

How can a CAA record break automatic certificate renewal?

For Let's Encrypt certificates with auto-renewal enabled, CAA records are checked every time auto-renewal runs. If CAA records are present and Let's Encrypt is not authorized, the auto-renewal will fail.

If you have a CAA record that doesn't include letsencrypt.org, Let's Encrypt will refuse to issue, which means your Certbot renewal will fail. This is a common cause of unexpected Let's Encrypt renewal failures. The certificate expires and traffic breaks. Automatic SSL systems, such as hosting panel SSL, CDN SSL or Let's Encrypt automation, can fail if CAA does not allow the CA being used.

The most common scenario: A domain sets a CAA record years ago, authorizing whichever CA was in use at the time. The old CAA record never gets updated, because updating a DNS record isn't usually part of anyone's migration checklist. The next renewal attempt from the new CA hits the CAA check and gets refused.

Before adding a CAA record, audit every certificate currently in use across the domain and all subdomains. If you use a hosting provider, CDN, or mail server that provisions certificates automatically, confirm which CA they use. Confirm whether your SSL certificate is issued by Let's Encrypt, DigiCert, Sectigo, GlobalSign, Google Trust Services, Amazon Trust Services or another CA. Then authorize all of them, or accept that some certificates will stop renewing. Use the free AI-visibility check (/check) to audit TLS configuration across multiple domains without manually checking each one.

What happens if I add no CAA record at all?

With no CAA record published, any publicly trusted CA may issue for your domain. If a domain has no CAA records at all, the default rule applies: any public certificate authority is allowed to issue a certificate for your domain, provided the applicant passes the standard domain validation checks.

This is not necessarily unsafe, it simply means the domain has no explicit restriction. A CAA record is optional. Without one, any publicly trusted certificate authority may issue certificates for your domain. For most MSPs, adding a CAA record is worth the five-minute effort once you know which CAs are actually issuing for each client domain. The operational risk lies in adding a CAA record and forgetting to authorize the CA that handles automatic renewal.

If you add one, test it. CAA records are only checked by the Certificate Authority before they issue or renew a certificate, so if a certificate was already issued, a CAA record does not revoke it or make browsers distrust it. CAA only constrains future issuance. For comprehensive DNS and TLS monitoring, including SPF, DMARC, and certificate health, consider the guide (/guide) on DNS security layers for managed services.

Common questions

What is a CAA record and how does it work?

A CAA record is a DNS record that specifies which certificate authorities are authorized to issue SSL certificates for your domain. If one or more CAA records are present, only the CAs explicitly listed are allowed to issue certificates. Certificate authorities are required to check the CAA record before issuing. Without a CAA record, any one of hundreds of publicly trusted certificate authorities can issue a certificate for your domain, which means an attacker who can demonstrate domain control, even temporarily through a DNS hijack or compromised email, can obtain a valid browser-trusted certificate.

What is the correct syntax for a CAA record?

The basic format is CAA 0 issue "ca-domain.com" where the flag is typically 0, the tag is issue, and the value is the CA's domain in quotes. For example, CAA 0 issue "letsencrypt.org" authorizes Let's Encrypt. There are three tags: issue for standard certificates, issuewild for wildcard certificates, and iodef for reporting violations. You can authorize multiple CAs by adding separate records with the same flag of 0. Common CA identifiers include letsencrypt.org, digicert.com, sectigo.com, pki.goog for Google Trust Services, and amazon.com for AWS Certificate Manager.

Do CAA records apply to subdomains automatically?

CAA records at the root domain apply to all subdomains unless a subdomain has its own CAA record. The CA will always respect the CAA record closest to the domain name it is issuing a certificate for, checking from the most specific subdomain up to the apex and stopping at the first CAA record it finds. This means a single CAA record at the apex protects the entire hierarchy, but a subdomain can have its own CAA rule that replaces the main domain rule for that specific name only. You only need subdomain-specific CAA records if you want different authorization for particular subdomains.

Can a CAA record break my Let's Encrypt auto-renewal?

Yes, CAA records are checked every time Let's Encrypt auto-renewal runs, and if the CAA record doesn't include letsencrypt.org, the renewal will fail. This is a common cause of unexpected renewal failures that lead to certificate expiration and broken traffic. The most common scenario happens when a domain sets a CAA record years ago authorizing a different CA, then migrates to Let's Encrypt without updating the CAA record. Before adding a CAA record, audit every certificate currently in use across the domain and all subdomains, confirm which CA your hosting provider, CDN, or mail server uses for automatic provisioning, and authorize all of them.

What happens if I don't add a CAA record at all?

With no CAA record published, any publicly trusted CA may issue for your domain, provided the applicant passes standard domain validation checks. This is not necessarily unsafe, it simply means the domain has no explicit restriction since a CAA record is optional. For most MSPs, adding a CAA record is worth the effort once you know which CAs are actually issuing for each client domain, but the operational risk lies in adding a CAA record and forgetting to authorize the CA that handles automatic renewal. CAA only constrains future issuance and does not revoke or invalidate certificates that were already issued before the record was added.