Skip to main content

How to fix: DNS Prefetch Explicitly Enabled

X-DNS-Prefetch-Control is set to 'on', leaking which links exist on the page.

Why it matters

DNS prefetching leaks which links exist to DNS servers and network observers.

DNS prefetching resolves domain names for all links before the user clicks them.

How to fix it

  1. 1Set X-DNS-Prefetch-Control: off for pages with sensitive links.
  2. 2Leave unset for public pages.

Code examples

Disable

text
X-DNS-Prefetch-Control: off

References

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

See every headers check

Questions

How severe is DNS Prefetch Explicitly Enabled?
VulnRadar rates this info severity in the headers 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-prefetch-on, 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 dns prefetch explicitly enabled

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: DNS Prefetch Explicitly Enabled | VulnRadar