What this site does with your address

Who runs this

dnsleak.dev is built and operated by SR WORKS LLC. The service, this site and its code are © 2026 SR WORKS LLC, all rights reserved. Nobody else is involved: there is no analytics vendor, no ad network and no third party with a view of your visit. The only requests that leave this server are the geolocation lookups described below, and the companies that receive one are named on this page.

What the test needs

Running the test means resolving hostnames under our own zone. Your resolver has to contact our nameserver to do that, so we see its address. That is the entire mechanism, and it is the only way this measurement is possible. We also see your address, because your browser made an HTTP request, the same as with any website.

What is kept

• Test results live in memory for ten minutes and are then discarded. They are not written to disk and there is no database.
• A daily tally of how many tests ran, how many completed and how many found a leak, and, for the API, what kind of software asked: a browser, a script, a named crawler or AI assistant. That is how we tell a busy day from a misbehaving bot. Counts only: no addresses, no user agents, no paths, nothing that could be tied back to a visit or reconstructed into one. Kept 90 days.
• A line for each request turned away for going over a rate limit: the time and which part of the site, so we can see a flood. No address, no user agent, no full path. Kept 14 days.
• A cache of resolver locations, so we stop asking about the same addresses. These are public infrastructure, the anycast machines Cloudflare, Google and NextDNS answer from, not visitors.

There are no cookies, no accounts, no logins and no advertising. Nothing about your visit is retained after those ten minutes.

What leaves the server

Working out where a resolver is takes data we do not have locally. Public resolvers are anycast, so one address is a hundred machines in a hundred cities, and offline databases fall back to whatever address the range was registered under, which is how a NextDNS server in Seattle gets reported as Dover, Delaware.

So some addresses are looked up with a geolocation service. This happens only when the offline databases cannot answer, or, for a resolver, when the two of them disagree about where it is, which is how a Canadian datacenter ends up pinned in Minnesota. Almost always that is a resolver; rarely it is a visitor whose network is missing from the offline data. An ordinary home or mobile connection is resolved on this machine and goes nowhere. Nothing else about you is ever sent: no browsing, no headers, no identifiers, and never the results of your test.

Any of the following may receive an address:

• IPinfo
• IPLocate
• ipwhois.io
• IP Guide

Nothing third-party in the page

The page itself loads nothing from anyone else: no analytics, no trackers, no tag managers, no CDN fonts. The WebRTC check uses our own STUN server rather than Google’s, which would have been one line shorter and would have broken the promise on the page that checks whether your address leaks.

Where the data comes from

• Offline IP databases by DB-IP Lite (CC BY 4.0), read on our own machine.
• Offline IP databases by MaxMind GeoLite2 (CC BY-SA 4.0), read on our own machine.
• Geolocation lookups by IPinfo.
• Geolocation lookups by IPLocate.
• Geolocation lookups by ipwhois.io.
• Geolocation lookups by IP Guide.
• Map outlines from Natural Earth (public domain), redrawn and served from this site.

Using the API

The API is free, needs no key and no account, and there is no bot filtering, because agents are a supported audience. Rate limits exist so one caller cannot spoil it for everyone; they are documented and generous. It is offered as-is, with no warranty and no uptime promise. Calling the API is free and encouraged; copying the site, its copy or its code is not covered by that.

A leak test is a measurement, not a guarantee. It reports what reached our nameserver during a few seconds. Treat it as evidence, not as proof that a configuration is safe.