CAA Record Setup: Restrict Which CAs Can Issue Your Certificates
The short answer (what's causing it)
Without a CAA record, any publicly trusted CA may issue a certificate for your domain. CAA (RFC 8659) lets you list the CAs you actually use.
Step-by-step fix
- List every CA you use (website, mail, CDN, MTA-STS host).
- Publish one
issueline per CA; addissuewildif you use wildcards. - Optionally add
iodeffor violation reports. - Scan free to confirm.
Record examples (replace example.co.uk with your domain)
example.co.uk. CAA 0 issue "letsencrypt.org"
example.co.uk. CAA 0 issue "sectigo.com"
example.co.uk. CAA 0 iodef "mailto:[email protected]"
Examples are illustrative templates, not values for your domain. Test changes at
p=none/ staging first.
Check yours free in seconds
Run the free 20-check SuperTool on your domain: no signup, no install, public DNS only. Relevant checks: CAA.
Scan my domain free (20-check SuperTool) → £19 NIS2, DORA & ISO 27001 Supplier Posture Bulk Auditor Pack → £5 Website Launch Special Quick-Fix Pack →One-off download via PayPal guest checkout, no subscription. Packs contain DNS/config templates and scripts you run yourself.
Frequently Asked Questions
Will CAA break my CDN?
It can if the CDN's CA isn't listed — check your provider's docs.
Do subdomains inherit CAA?
Yes, CAs climb the tree until they find a record.
Related FaultyPacket guides & tools
- Free 20-check SuperTool
- NIS2 & DORA supplier posture auditor
- Website hosting & MX records DNS setup 101
Authorised use: only scan domains you own or are authorised to inspect. Results are point-in-time public DNS observations.