Privacy
A DNS tool that quietly tracked you would be self-defeating. Here is exactly what happens when you run a check.
Visitor analytics: the provider and the cookies
Visitor analytics is provided by Lovable, the platform that hosts this site. Its script is served from this same domain rather than from a third-party analytics host, and the counts it reports go back to that same domain.
That analytics sets one cookie. A second cookie is set by Cloudflare, which delivers the site. The two are listed below with what each one does and how long it lasts — you can check them against your browser’s cookie panel.
No AMP_, AMP_MKTG_ or session-id cookies are set: this site runs no Google Analytics and no AMP analytics. No advertising trackers, tag managers or cross-site behavioural pixels run here.
The site loads no advertising scripts, fonts from a CDN or icon stylesheets from a CDN. The DNS check itself contacts the measurement services listed below.
Country flags are Unicode emoji. On systems without flag emoji (such as Windows), a small flag font is loaded from this site. No image host or font CDN is contacted.
- __dpl
- About 1 day, refreshed each time you visit
- Visitor analytics, provided by Lovable, the platform that hosts this site. It holds a random identifier so that one visit is counted as one visit rather than as every page request. It carries no DNS result and no IP address.
- __cf_bm
- 30 minutes
- Bot management, provided by Cloudflare, which delivers this site. It lets the network tell an ordinary browser from an automated script before the page is served. It is marked HttpOnly, so page scripts cannot read it.
Neither cookie is used for advertising, and neither is joined to a DNS result. Analytics is the platform’s visitor analytics and it is active on this site.
What we store when you run a check
The DNS scan result runs in memory and is discarded when you close the tab. There is no account and the scan result is not attached to an analytics record.
WebRTC is off by default. Only if you enable WebRTC check under Advanced options does a separate check gather browser connection candidates after DNS results appear. Only public addresses are retained in this tab’s memory, until you leave the results or close the tab. They are never sent to our server, analytics, daily counters or Explain with AI, and are not written to browser storage. The opt-in choice is not saved and resets when you reload.
Your VPN answer is used on your device to interpret the result. When an intentional audit finishes, it is sent only to increment independent daily totals; it is not saved as an individual answer or joined to a visitor analytics record.
If you have not picked an answer yourself, the page may pre-select one from your connection’s AS number alone — “No” when that network is on our list of consumer internet providers, “Yes” when it is on our list of networks widely used by VPN services. Nothing on your device is inspected, the pre-selection is cleared when you reload the page, and choosing an answer yourself switches it off for that visit.
“Incorrect?” opens an inline VPN choice. Choosing Yes or No updates the explanation on your device using the same measured DNS servers, and adds only your answer and connection’s AS number to independent daily review totals. Merely opening the choice or choosing Not sure sends no report; Not sure restores automatic detection. Your IP address is never included in the report, and the report is not joined to a check result. Reports appear for manual review and never automatically change our network lists.
Nothing about a check is written to your browser’s storage: DNS results and VPN answers are not stored in localStorage or sessionStorage. localStorage stays empty both before and after a run.
The one entry this site writes to sessionStorage is tsr-scroll-restoration-v1_3. It holds page scroll positions so your place on a page is remembered when you move between pages, and it is thrown away when you close the tab. No personal or network data is stored in it.
Server logs may contain request metadata as a normal function of hosting, but no scan result is ever written to a database.
After your connection is identified, the page quietly makes six DNS lookups while you choose your settings. No result is revealed and no additional lookups are made until you press Check my DNS. These observations stay in memory, expire after two minutes, and are reused only if a fresh connection check still matches. Background work that you never confirm is not counted as an intentional audit.
To see how the tool is used, we keep daily totals for intentional audits and deeper checks — separate tallies for country and network number (from our hosting network’s metadata), test depth, VPN answer, overall result and DNS provider names seen. Background audits add their totals only when you request and complete the result. Each counter is a number for that day and nothing else, with no time of day, IP address, session or device identifier, so no single check can be rebuilt from them.
Explain with AI
Explain with AI builds a prompt and a summary of your result on your device. You choose what to include and preview the exact text; individual DNS server IPs are off by default and your own IP is never included. Pressing copy puts it on your clipboard. Nothing is sent to an AI service, our server or analytics, and nothing is stored. Once you paste it into an AI chat, that service’s privacy policy applies.
The summary never includes your own IP address. DNS server addresses are included because they identify DNS services, not you — except servers on your own subnet, which are shortened (203.0.113.47 becomes 203.0.113.x). IPv6 appears only as “active: yes/no”.
Once you paste it into an AI assistant, that service’s privacy policy applies.
Share links have been retired, and previously saved results have been deleted. No scan result is stored on our side.
Third parties involved in a check
bash.ws operates the authoritative nameserver that observes which resolver looks up your probe hostnames. They necessarily see those lookups — that is the measurement. A serverless app cannot bind UDP port 53, so this step has to be delegated.
Your ISP, ASN and location are read first from metadata our hosting network (Cloudflare) already attaches to your request. When that is unavailable, our server — not your browser — asks ip-api.com, then freeipapi.com, then ipapi.co, stopping at the first answer. Your IP is sent to whichever of them is asked. ip-api.com is also used to look up the DNS servers found.
api4.ipify.org and api6.ipify.org are queried directly by your browser to detect your public IPv4 and IPv6 addresses. These services necessarily receive your IP address and standard request metadata.
Only when you opt in, the optional WebRTC check contacts Cloudflare’s public STUN service at stun.cloudflare.com:3478 and Google’s at stun.l.google.com:19302 directly from your browser. With WebRTC off, neither STUN service is contacted. Both providers necessarily receive the source IP and port of traffic reaching them. These are third-party measurements subject to their respective privacy policies; we do not claim that either provider stores nothing. No camera or microphone access is requested, no call is made, and no candidate addresses are sent to another peer. Retrying the WebRTC check contacts these services again.
AS numbers link to Cloudflare Radar. Nothing is sent to Cloudflare unless you click one of those links.
The method is published
We do not infer what kind of service a resolver is. An IP address cannot tell you whether a resolver belongs to a VPN, a filtering service or someone’s home server, so we report the operator name and network and stop there.
© 2026 DNS Leak Audit