Security & CertificatesRFC 8659

CAA Record β€” CAA Record (Certification Authority Authorization)

Specifies which Certificate Authorities (CAs) are permitted to issue TLS/SSL certificates for your domain.

RECORD TYPE

CAA

STANDARD RFC

RFC 8659

DEFAULT TTL

3600 seconds (1 hour)

CATEGORY

Security & Certificates

BIND Zone File Syntax Example

example.com. 3600 IN CAA 0 issue "letsencrypt.org" example.com. 3600 IN CAA 0 issuewild ";" # Prohibits wildcards

How to Query & Check CAA Records

Linux / Mac (dig)
dig +short CAA example.com
Windows / Generic (nslookup)
nslookup -type=CAA example.com
PowerShell (Resolve-DnsName)
Resolve-DnsName -Name example.com -Type CAA

Recommended Best Practices

If using Vercel, AWS CloudFront, or Cloudflare, ensure you authorize their respective CAs (e.g. `letsencrypt.org`, `digicert.com`, `amazontrust.com`) to prevent SSL renewal failures.

Primary Use Cases:
  • β€’Restricting SSL issuance strictly to Let's Encrypt (`letsencrypt.org`) or DigiCert
  • β€’Forbidding wildcard certificate creation (`issuewild ";"`) to mitigate subdomain hijacking
  • β€’Receiving automated security notifications (`iodef "mailto:security@example.com"`) if unauthorized issuance is attempted

Common Configuration Mistake

Adding a CAA record that excludes your hosting provider's automated SSL issuer, causing HTTPS renewal to fail and triggering browser security warnings.

Always verify records using authoritative queries (`dig @1.1.1.1 $CAA example.com`) to bypass local ISP caching when debugging propagation delays.
Frequently Asked Questions

DNS CAA Record Questions & Answers

Common questions regarding DNS propagation, TTL settings, and zone file syntax.

CAA (Certification Authority Authorization) prevents rogue or compromised Certificate Authorities from issuing fraudulent SSL certificates for your domain. CAs are legally mandated by the CA/Browser Forum to check CAA records before certificate issuance.