How it works

DNS resolver detection relies on a clever trick — there is no browser API that exposes which DNS server you use. Here is how the measurement actually works.

01

Unique hostnames are generated

Once your connection is identified, the page quietly observes six unique hostnames while you choose your settings. Check my DNS rechecks your connection and applies your current VPN, expected-provider and depth choices to those observations. Adaptive adds 30 more lookups only when the existing evidence warrants them; Extended always requests the additional batch. Both reuse the same session. Observations older than two minutes or from a changed connection are replaced. No DNS cache holds these unique names, so each lookup travels to the authoritative nameserver.

02

Your browser resolves them

Your browser asks whichever recursive resolver your OS or router is configured to use. That resolver — your actual DNS server — doesn't know the answer, so it queries the authoritative nameserver to find out. The lookup reaches the nameserver regardless of whether the HTTP request itself succeeds.

03

The nameserver logs who asked

The source IP is the public egress address of the recursive resolver that handled the lookup. With DNS-over-HTTPS, this may be an edge node in a Cloudflare, Google or other resolver cluster rather than the familiar anycast address entered in your browser. This page reports that observed address, its network, AS number and registry location.

Frequently asked questions

What does the WebRTC check measure?

WebRTC check is optional and off by default. Enable it under Advanced options before running the audit. Only then, after DNS results appear, the browser gathers WebRTC connection candidates using Cloudflare and Google public STUN services, without a call or camera or microphone access. Public candidate addresses are compared with your web connection’s IPv4 and IPv6 addresses separately. A different address can indicate a different network path, but does not by itself prove a VPN leak. Matching addresses do not guarantee protection. Gathering concludes a few seconds after the last address arrives; a 25-second safety limit covers networks that never answer, and any addresses collected by then are still compared and clearly marked partial. No STUN response means the check could not collect a public address, not that you are protected or leaking; browser privacy controls, VPN rules, network restrictions or unavailable services can explain it. You can retry from Details without rerunning DNS or disabling privacy settings. The check never changes the DNS verdict. Addresses remain in this tab and are excluded from Explain with AI.

What do the network badges mean?

Same network means the resolver and your connection share a published AS number, network owner, or—when AS data is unavailable—a directly comparable IP subnet. Third-party DNS means the resolver answered from a network other than your connection’s — typically a public resolver such as Cloudflare, Google or Quad9 that you or your network chose. When connection and DNS use different network numbers that both belong to the same verified operator family—such as a mobile network and its sister transit network—the result is reported as Same provider group rather than a mismatch. The audit reports the relationship without deciding whether it is expected for your setup.

Why can't you just ask my browser which DNS server it uses?

Browsers intentionally hide this. DNS configuration is an OS-level detail that the browser sandbox cannot read. The only reliable way to observe it is to make the browser perform a lookup and watch who comes asking at the authoritative nameserver.

What is a recursive resolver?

When you type a domain into your browser, your OS sends the query to a recursive resolver — a server that does the legwork of finding the answer. Most people use the one their ISP assigns automatically via DHCP. Others configure a different resolver, such as 1.1.1.1, 9.9.9.9, or one provided by software running on their network.

Do you guess what kind of DNS service I am using?

No. An IP address does not reveal whether a resolver belongs to a VPN, a filtering service or a private server — plenty of DNS services run on shared hosting networks, so any such label would frequently be wrong. This page reports only what is published about each resolver: its IP, network owner, AS number and location.

Why does the result ask whether I am on a VPN?

A browser cannot see whether a VPN is running. We compare the network your connection comes from with the networks that answered your lookups. “Incorrect?” lets you correct the automatic assumption inline with Yes, No or Not sure; Change lets you revise it. Completed explanations update from your answer without changing the measured DNS servers or running another check. Saying Yes does not establish a protected tunnel: if your connection and DNS still appear on a consumer ISP, we explain that mismatch rather than show a green result. Unknown networks still offer the VPN question in the result. Answers are held in memory and cleared when you reload; review reports contain only the AS number and Yes/No answer, never the result or your IP.

Does the page ever answer the VPN question by itself?

Sometimes, and only from the AS number of your connection. If that network is on our list of consumer internet providers, “No” is pre-selected; if it is on our list of networks widely used by VPN services, “Yes” is. Nothing on your device is read — it is the same lookup the page already makes to name your provider. A pre-selection is a starting point rather than a conclusion: pick an answer yourself and the automatic choice stops for that visit, and either way it is cleared when the page reloads.

Why does the operator name differ from the network owner?

Registry strings are often written in shorthand — CLOUDFLARENET rather than Cloudflare. Where an operator is well known, the normal spelling is shown instead. Nothing else is changed.

What if nothing is detected?

An ad-blocker or privacy extension may have blocked the probe requests before they triggered a DNS lookup. Browser-level DNS-over-HTTPS can also route queries through a resolver that is not visible at the network level. Try temporarily disabling extensions and scanning again.

Who observes the DNS queries?

This app delegates the authoritative nameserver step to bash.ws, which runs an authoritative nameserver for *.bash.ws and exposes the resulting query log as JSON. The hosted app cannot listen for DNS traffic on port 53 itself. The code also supports a separately operated authoritative nameserver and query-log service.

Does Extended mode guarantee IPv6 resolver detection?

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. Extended mode sends more unique lookups and waits longer, which improves the chance of seeing slower IPv6 paths and rotating resolver pools. The current probe domain does not provide separate IPv4-only and IPv6-only names, so a browser cannot be forced to use a distinct IPv6 DNS path. Only resolvers actually observed are reported.

How many lookups does a test run?

The result card reports what your DNS servers are, not how many lookups it took. Explain with AI includes the test mode, whether Adaptive added extra lookups, and how many probe hostnames were attempted. That count is separate from the number of DNS servers found, which appears with the server list.

How does the expected vs actual check work?

Open Advanced options before running the audit to optionally select Cloudflare, Google Public DNS, Quad9 or OpenDNS — or, when you are not on a VPN, your own connection’s provider, so you can verify traffic stays with your internet provider. We compare that provider with every resolver observed. A partial match means some observed resolvers matched the selected provider and others did not. No provider is selected during the basic audit.

What happens when my DNS spans several providers?

The headline names the provider handling your lookups, or says they are split between two, or names the main one plus how many others when there are three or more. Every observed resolver is still listed below.

What happens when I copy a result for AI?

Explain with AI builds a prompt and summary on your device and lets you preview it before copying. It never includes your own IP address; individual DNS server IPs are off unless you include them, and servers on your own subnet are shortened. Nothing is sent to or stored on our server. Once you paste it into an AI assistant, that service’s privacy policy applies.

© 2026 DNS Leak Audit