Skip to main content
MediumDNSOWASP A02:2021CWE-295

How to fix: CAA Record Present But Restricts No Certificate Authority

A CAA record set exists for this domain, but none of its records use the 'issue' property tag. Per RFC 8659, the absence of an 'issue' tag means non-wildcard certificate issuance is unrestricted, so the CAA record provides no actual protection against certificate misissuance.

Why it matters

Despite a CAA record existing, any publicly trusted CA can still issue a certificate for this domain, the same exposure as having no CAA record at all. Anyone auditing DNS and seeing a CAA record present may mistakenly assume issuance is restricted.

RFC 8659 defines the 'issue' property tag to authorize CAs for non-wildcard certificates and 'issuewild' for wildcard certificates, falling back to 'issue' when 'issuewild' is absent. If a CAA record set contains only other tags, for example an 'iodef' violation-reporting address, with no 'issue' tag at all, there is no applicable restriction and any CA may issue.

How to fix it

  1. 1Add at least one CAA record with the 'issue' property tag naming your authorized CA(s).
  2. 2Example: 0 issue "letsencrypt.org"
  3. 3Keep any existing iodef reporting record alongside it.
  4. 4Verify with: dig +short CAA yourdomain.com

Code examples

DNS zone file

DNS
example.com. IN CAA 0 iodef "mailto:[email protected]"  ; reporting only, no restriction
example.com. IN CAA 0 issue "letsencrypt.org"              ; add this to actually restrict issuance

References

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

See every dns check

Questions

How severe is CAA Record Present But Restricts No Certificate Authority?
VulnRadar rates this medium 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-no-issue-restriction, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does CAA Record Present But Restricts No Certificate Authority map to?
It maps to CWE-295. In the OWASP Top 10 it falls under A02: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 present but restricts no certificate authority

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 Present But Restricts No Certificate Authority | VulnRadar