CAA record check: control which CAs can issue certificates
A CAA (Certification Authority Authorization) DNS record lists the certificate authorities allowed to issue TLS certificates for your domain. Every public CA must check it before issuing, so a stray or fraudulent certificate from another CA is refused. SiteShield passes a domain with a CAA record and warns without one (2 of 100 points).
What is CAA record?
CAA records (RFC 8659) have a flag, a tag and a value. issue authorises a CA for normal certificates, issuewild for wildcard certificates, and iodef gives an address to report refused requests to. If no CAA record exists, any CA may issue.
(no CAA record: any of the hundreds of public CAs may issue)example.com. CAA 0 issue "letsencrypt.org"
example.com. CAA 0 issue "pki.goog"
example.com. CAA 0 iodef "mailto:security@example.com"Why it matters
A CAA record limits which certificate authorities may issue certificates for your domain, making fake certificates harder to obtain.
Certificate authorities have mis-issued certificates in the past through validation mistakes or compromised accounts. A CAA record means only the CAs you actually use can issue for you, which shrinks that risk. Checking CAA has been mandatory for public CAs under the CA/Browser Forum Baseline Requirements since September 2017.
SiteShield maps this check to:
See how these standards fit together in the UAE website security checklist.
How SiteShield grades it
This check, "CAA record", can cost up to 2 points: a fail loses all 2, a warning loses 1. Every scan starts at 100.
| Result | When | Points lost |
|---|---|---|
| Pass | A CAA record exists on the scanned domain. | 0 |
| Warning | No CAA record on the scanned domain. | 1 |
| Not checked | The lookup failed. | 0 |
SiteShield looks up CAA on the exact domain scanned. CAs also honour a CAA record on a parent domain, so a subdomain scan can warn even when the parent has one.
How to check it yourself
dig +short CAA example.com
# 0 issue "letsencrypt.org"
Or run a free SiteShield scan, which checks this and 16 other settings in one go.
How to fix it
The quick version: Add a CAA record, e.g. 0 issue "letsencrypt.org" (list the CAs you actually use).
Find your CAs first
Look at the issuer of your current certificate (click the padlock) and of any certificates on subdomains, mail servers and CDNs. Common values: letsencrypt.org, pki.goog (Google Trust Services), digicert.com, sectigo.com, amazon.com (AWS).
Cloudflare
- DNS → Records → Add record, Type
CAA, Name@, tag Only allow specific hostnames, CA domain name e.g.letsencrypt.org. Add one record per CA. - With Cloudflare's Universal SSL, Cloudflare adds the CAA records for the CAs it uses itself once you add your own, so your edge certificate keeps renewing.
Other DNS hosts
Most DNS panels have a CAA type; enter flag 0, tag issue and the CA's domain. In zone-file form:
example.com. 3600 IN CAA 0 issue "letsencrypt.org"
example.com. 3600 IN CAA 0 iodef "mailto:security@example.com"Nginx / Apache / WordPress
Not applicable: CAA is a DNS record. Your host's certificate (often Let's Encrypt) must be listed, or renewals will fail.
FAQ
Can a CAA record break certificate renewal?
Yes, if you forget a CA you use. Renewals from an unlisted CA are refused. List every CA behind your site, subdomains and CDN before adding the record.
Do I need issuewild?
Only if you want different rules for wildcard certificates. Without issuewild, the issue records apply to wildcards too.
Test your CAA record now
Run all 17 checks on your website and email domain in about 30 seconds. Free, no signup, passive checks only.
Rather not do it yourself? Fix it for me starts at AED 750 (about USD 205 by PayPal), quote agreed first. Monitoring re-scans weekly for AED 99/month or AED 990/year.