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.

Are you using a VPN right now?

The test can't tell what you meant to use, so your answer changes how the result is worded. If you leave it, the result covers both cases.

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.

Other tools

IPv4 · IPv6 · CIDR
Subnet calculator
Network, broadcast, host range and wildcard for any CIDR, IPv4 or IPv6. Turns an IP range into the CIDR blocks that cover it.
OUI · MA-L · MA-M · MA-S
MAC vendor lookup
Which company made the device behind a hardware address, from the IEEE registry. Spots randomised private addresses too.
X.509 · PKCS#10 · PEM · DER
Certificate and CSR decoder
Subject, issuer, validity, key, SANs, key usage and fingerprints from a certificate or signing request. Parsed in your browser.
Cloudflare · Google · Quad9 · 8 resolvers
DNS benchmark
Times eight public resolvers from where you are, over DNS-over-HTTPS, and ranks them by median response.
TCP · UDP · what is this port
Port lookup
What a port number is used for, which home devices open it, and whether it matters that it is reachable.
Certificate Transparency · CT logs
Subdomain finder
Every subdomain on a currently valid TLS certificate, from the public Certificate Transparency logs, with the ones worth a second look flagged.
IP to ASN · BGP · IP ranges
ASN lookup
Which network routes an IP address, who holds an AS number, and every IPv4 and IPv6 range it announces. Live BGP data from RIPEstat.
HTTP archive
HAR analyzer
Open a HAR file and see what a page really loaded: third parties, slowest requests, insecure cookies, servers that leak versions.
IIS · nginx · Apache · access logs
Log analyzer
Check IIS, nginx and Apache access logs for signs of exploitation, with a verdict per CVE and every finding traced to its line. Read in your browser, never uploaded.
Public IP · fingerprint
What is my IP
Your public address and everything else your browser hands to every site you visit, without asking.