Who answers your DNS lookups?
Before your browser opens a site, it asks a DNS server where to find it. Whoever runs that server can see which sites you look up. This test shows which servers answered this browser, and who runs them.
Takes about 5 seconds and uses the internet. Your browser looks up a few one-off test names on our server. It notes which DNS servers asked, and your IP address so it can show who carries your traffic. The test session is deleted after 10 minutes.
What a DNS leak is
When you use a VPN, your traffic is supposed to travel inside the tunnel, including the lookups that turn names into addresses. A leak is when those lookups go outside it: your device keeps asking the resolver your ISP assigned, so the ISP still gets a running list of every site you visit even though the page content is hidden. It happens with misconfigured VPN clients, split tunnelling, IPv6 on a VPN that only handles IPv4, and operating-system features that try every resolver at once to be faster.
How this test works
Your browser requests a handful of names that have never existed before, all under a domain whose DNS server we run. Nothing in the world has those names cached, so the resolver your device is using has no choice but to ask our server for them, and our server writes down who asked. The page then reads that list back. Your own address never reaches the DNS side; only your resolver's does. The page's request for the result carries your address, and both are looked up in the routing registry to name the network that owns them.
Reading the result
The test compares two networks: the one that owns the DNS servers answering this browser's lookups, and the one this browser's traffic leaves from. The same network for both is the usual setup without a VPN, where your provider does both; on a VPN, it means the VPN's network is answering. Different networks on a VPN are a possible leak, unless the VPN is set to use that DNS service; without a VPN, a proxy, an extension, iCloud Private Relay or a public DNS setting is the usual reason. Many addresses from one owner are a large provider's fleet of servers, not several leaks. A server in a country you did not expect is worth understanding, since that operator sees your lookups and answers under its own laws.
What it does not tell you
Whether the answers you get are honest. A resolver can see your lookups without a leak, and a hostile network can rewrite answers without ever appearing here. Testing for that needs a known-good answer to compare against, which is a different check. It also cannot see DNS-over-HTTPS traffic that a browser sends on its own; if your browser has secure DNS enabled, the resolver shown is the one it chose, not the one your operating system uses.