Skip to main content
InfoDNSOWASP A09:2021CWE-778

How to fix: CAA record names no incident reporting address

The domain publishes CAA records restricting certificate issuance, but no iodef property. A CA that receives a request violating the policy therefore has nowhere to report it.

Why it matters

The iodef property is the only channel that turns a blocked issuance into a signal you actually receive. Without it, someone attempting to obtain a certificate for your domain from a CA you have not authorised is quietly refused and you never learn the attempt happened, which is exactly the early warning worth having.

This is a hygiene recommendation rather than a weakness: the issuance restriction itself is working, and that is the part that matters most. RFC 8659 defines iodef as a mailto or https URL that a CA may use to report policy violations. Reporting is discretionary rather than mandatory, so treat it as one useful input alongside Certificate Transparency monitoring, not as a guaranteed alert.

How to fix it

  1. 1Add a CAA iodef record pointing at a monitored mailbox or ticket queue rather than an individual.
  2. 2Pair it with Certificate Transparency monitoring, which catches issuance that actually succeeded.
  3. 3Re-check the full CAA set at the same time: issue, issuewild and iodef are decided together.

Code examples

CAA with restriction and reporting

DNS
example.com. IN CAA 0 issue "letsencrypt.org"
example.com. IN CAA 0 issuewild ";"
example.com. IN CAA 0 iodef "mailto:[email protected]"

Check what is published

bash
dig +short CAA example.com

References

Detected automatically by VulnRadar. The check id is dns-caa-iodef-missing, stable across every scan so you can filter or diff on it.

See every dns check

Questions

How severe is CAA record names no incident reporting address?
VulnRadar rates this info severity in the dns category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id dns-caa-iodef-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does CAA record names no incident reporting address map to?
It maps to CWE-778. In the OWASP Top 10 it falls under A09:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for caa record names no incident reporting address

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

CAA record names no incident reporting address | VulnRadar