How to fix: CAA Record Restricts Wildcard Certificates Only
The CAA record set for this domain includes an 'issuewild' property tag but no 'issue' property tag. Per RFC 8659, 'issuewild' only governs wildcard certificate requests, so ordinary (non-wildcard) certificate issuance remains unrestricted.
Why it matters
Any publicly trusted CA can still issue a standard, non-wildcard certificate for this domain, even though wildcard issuance is correctly restricted. This is a narrower gap than having no CAA record, but a single misissued non-wildcard certificate is enough for a MITM against a specific hostname.
RFC 8659 S4.2 defines 'issue' as the property tag that authorizes CAs for non-wildcard certificates. 'issuewild' only applies to wildcard requests: when present it takes over from 'issue' for those requests, but it never substitutes for a missing 'issue' tag on ordinary certificates.
How to fix it
- 1Add an 'issue' record naming the same CA(s) already listed under issuewild.
- 2Example: 0 issue "letsencrypt.org"
- 3Verify with: dig +short CAA yourdomain.com
Code examples
DNS zone file
example.com. IN CAA 0 issuewild "letsencrypt.org" ; wildcard only
example.com. IN CAA 0 issue "letsencrypt.org" ; add this for non-wildcard certs tooReferences
Detected automatically by VulnRadar. The check id is dns-caa-wildcard-only-restriction, stable across every scan so you can filter or diff on it.
More dns checks
Questions
- How severe is CAA Record Restricts Wildcard Certificates Only?
- VulnRadar rates this low 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-wildcard-only-restriction, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does CAA Record Restricts Wildcard Certificates Only 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.