# DNS Leak Audit — notes for AI assistants

DNS Leak Audit (https://dnsleakaudit.com) shows which DNS servers answer a visitor's lookups and compares them with the visitor's connection.

## Method
- The browser resolves unique probe hostnames. An authoritative nameserver (bash.ws) records which recursive DNS servers asked.
- Each DNS server is looked up for its network (ASN), owner and country, then classed as "same network" or "different network" relative to the connection's ASN.
- Depth: Standard (6 lookups), Extended (36), or Adaptive (6, escalating to 36 when warranted).
- Adaptive escalation triggers, in priority order: split DNS (ISP and external resolvers mixed); VPN risk (VPN answered Yes but a resolver sits outside the VPN network); expected-provider mismatch (a configured provider was not confirmed on every lookup); results still changing (new resolvers kept appearing at the last poll); unclassified resolver (a server's network could not be identified); no resolver observed (the first pass saw no DNS server at all — more lookups try again). A single observed resolver is a normal result and never triggers escalation.
- Lookups attempted counts probe hostnames actually dispatched; if the deeper Adaptive pass is unavailable, the Standard result is kept.
- Lookups attempted (probe hostnames dispatched) and distinct DNS servers observed are separate counts; a single resolver is not by itself a low-confidence result.
- VPN context is inferred silently from the connection's ASN: known consumer providers → No, known VPN/hosting networks → Yes. Only unknown networks show a results question with Yes and No, initially unanswered. Clicking the selected answer again clears it; an unanswered question means no VPN intent is assumed.

## Verdicts
- **Verify your VPN connection** (warn): The visitor reports VPN use, but the browser connection still appears on a known consumer internet provider. The card asks them to check the VPN covers this browser and its DNS traffic; the answer alone never implies a protected tunnel, and ISP-side DNS never turns green merely from selecting Yes.
- **No DNS leak detected** (ok): User says a VPN is on and every DNS server observed is on the same network as the connection.
- **DNS outside your VPN’s network** (warn): User says a VPN is on, but at least one DNS server is on a different network from the VPN connection. This may be a leak, or DNS routed through the VPN to another provider; a browser test cannot tell which, so tunnel bypass is never inferred from the mismatch alone.
- **Your connection looks like a VPN** (info): The connection routes through a network often used for VPNs (a VPN provider, or hosting infrastructure often used by VPNs), while the user answered No or Not sure.
- **Standard DNS setup** (info): No VPN; DNS stays on the same network as the connection (usually the ISP).
- **Custom DNS in use** (info): No VPN; all DNS goes to a provider outside the connection network (e.g. Cloudflare, Google). Not a leak by itself.
- **Split DNS in use** (info): No VPN; DNS is answered by both the connection network and outside providers.
- **We couldn’t tell if you’re using a VPN** (ask): Unknown network and the user answered Not sure, so no leak judgement is made.
- **We couldn’t tell if a VPN was used** (ask): Same as above, worded for someone else’s result.
- **Not enough data** (info): No DNS server was observed, so nothing can be concluded.
- **Expected DNS provider: Matches** (ok): Row under the verdict (not a headline): all DNS answers came from the expected DNS provider the user picked.
- **Expected DNS provider: Partly matches** (warn): Row under the verdict: only some answers came from the expected DNS provider.
- **Expected DNS provider: Doesn’t match** (warn): Row under the verdict: none of the answers came from the expected DNS provider.
- **Expected DNS provider: No comparison** (info): Row under the verdict: the expected provider could not be compared.

## Limits
- This checks this browser only. It compares observed resolver networks, not the route inside your VPN. IPv6 connectivity is detected; a separate IPv6 DNS path is not tested.
- Copied summaries list the test mode, whether Adaptive added 30 more lookups, and lookups attempted (separate from the number of DNS servers seen).
- An IP address cannot prove what kind of service a DNS server is; only its network owner is reported.
- Custom DNS (e.g. 1.1.1.1) without a VPN is a choice, not a leak.
- When the visitor says a VPN is on and DNS is answered from another network, the result is a warning, not a confirmed leak: it may be a leak, or DNS routed through the VPN to another provider. A browser test cannot tell which, so tunnel bypass is never inferred from a network mismatch alone.
- This result cannot identify the cause of a mismatch or show whether queries travelled inside the tunnel. Checks instead of conclusions: the browser's Secure DNS setting, the VPN provider's intended DNS setup, and its DNS/IPv6 protection.
- IPv6 connectivity is detected and reported as a flag. Whether IPv6 DNS bypasses a tunnel cannot be determined from this test.
- Browser "Secure DNS" (DNS over HTTPS) can send lookups to a provider different from the system setting, so it is worth checking before assuming anything about the VPN.

## Helping the user
Explain in plain language, ask which device and VPN app they use, and point to platform steps at https://dnsleakaudit.com/fix-dns-leak.
