Skip to main content
LowDNS

How to fix: Wildcard DNS Record Detected

A randomly generated, never-created subdomain resolved successfully, meaning this domain has a wildcard DNS record (*.example.com) that answers for any subdomain, whether or not it was intentionally created.

Why it matters

Every possible subdomain resolves, whether or not it was intentionally created. Phishing pages hosted at unexpected subdomains (login.example.com, secure-verify.example.com) inherit the domain's trust and any wildcard TLS certificate, and if the wildcard target is a shared or reassignable resource, it also widens the subdomain-takeover surface: an attacker no longer needs to find an existing dangling record, any name they pick already resolves.

A wildcard DNS record (RFC 1034 S4.3.3) answers queries for any subdomain that doesn't have its own explicit record. This check queries a random 16-character subdomain that was almost certainly never created; if it resolves anyway, a wildcard record is in effect. Wildcards are sometimes intentional (multi-tenant SaaS platforms, preview-branch hosting), so this finding is a prompt to confirm the wildcard is deliberate and scoped correctly, not proof of a misconfiguration on its own.

How to fix it

  1. 1Confirm the wildcard is intentional. If not, remove the * record and add explicit records only for subdomains actually in use.
  2. 2If the wildcard is intentional, make sure its target cannot be hijacked (avoid pointing it at a de-provisionable cloud resource) and that any wildcard TLS certificate is scoped and monitored the same as other certificates.
  3. 3Verify with: dig +short A random-string-that-does-not-exist.example.com

Code examples

Verify wildcard

bash
dig +short A $(openssl rand -hex 8).example.com
# A non-empty answer for a name you never created confirms a wildcard record

References

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

See every dns check

Questions

How severe is Wildcard DNS Record Detected?
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-wildcard-record-present, 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.

Propose a checkHow a check is built

Scan your own site for wildcard dns record detected

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

How to fix: Wildcard DNS Record Detected | VulnRadar