How to fix: DNS A/AAAA Resolution
Async check: resolves A and AAAA records for the target hostname. Reports whether the domain resolves at all and flags private, loopback, or link-local addresses that should not appear in public DNS.
Why it matters
Private IPs in public DNS reveal internal network topology and can indicate dangling records or takeover risk for cloud-provisioned addresses.
DNS resolution is the first step of every scan. If the resolver returns RFC1918 (10.x, 172.16-31.x, 192.168.x), loopback (127.x), or link-local (169.254.x) addresses for a public hostname, the target may not be publicly reachable or may expose internal infrastructure.
How to fix it
- 1Remove A/AAAA records pointing to internal or private IP ranges from public DNS.
- 2Audit CNAME chains for dangling-takeover risk (Cloudfront, Heroku, GitHub Pages, etc.).
- 3Use split-horizon DNS only where appropriate and audit both views.
Code examples
Check A and AAAA
dig +short A example.com
dig +short AAAA example.comReferences
Detected automatically by VulnRadar. The check id is dns-resolves, stable across every scan so you can filter or diff on it.
More dns checks
Questions
- How severe is DNS A/AAAA Resolution?
- 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-resolves, which stays the same between runs so you can filter, diff, or gate CI on it.
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.