isitdns? it's always dns  until it isn't

Privacy

privacy

Testing your own path, VPN or DNS provider here keeps no address, no name and no query. Each web request leaves one count row (time, route, method, status, refusal reason, latency); DNS queries are counted by the hour.

That covers the test names under probe.isitdns.net (canary, who, whoami and the fresh names a test makes), the dig reader's compare (/api/compare), the network diagnosis (/api/diagnose) and the path receipt (/api/path-receipt). Lookups through /dig, curl and the MCP tools are not path tests; for those, the rest of this page applies.

Lookups you send to isitdns are logged: what you asked, when, and how it went. Your IP address and user agent are logged only when the request fails or is refused. During a flood, lookups past the logging limit are not written; MCP calls past it are still counted, with no address.

This page covers isitdns.net: the site, the API, the CLI surface (curl), the MCP server and DNS queries to the isitdns.net zone.

Before you send anything: a lookup that works is written with no address and no user agent; one that fails or is refused keeps both for 30 days, traceable by them. The feedback and question forms keep what you type, your country and a daily hash of your address, as the list below says.

purposes

I use this data only for the purposes listed below.

  • Run the service and fix wrong or missing readings.
  • Enforce the rate limit: 100 requests a minute per address.
  • Find and stop abuse.
  • Count use: requests a day, by tool and by client type.
  • Feedback: see which pages work for readers.
  • Questions: answer them.
  • Probe signups: reply about hosting a probe.
  • Probe reports: show and check each probe's readings.
  • Name server counts: see that the probe zone answers, and how much.
data collected

For every MCP tool and API route but /api/compare, /api/diagnose and /api/path-receipt, the log stores the tool or route and every argument sent, up to 2,048 characters.

fieldwhat is writtenwhy
timeWhen the answer was ready, to the millisecond.Orders the log and starts the 30-day clock.
IP addressIn full, as Cloudflare passes it. Failed or refused requests only.Abuse handling, and finding your rows for an access or deletion request.
user agentThe first 512 characters sent. Failed or refused requests only. MCP rows keep the client type (browser, curl, SDK, Claude, ChatGPT, probe), and dig and check rows whether the request came from a browser on this site.Which client asked, to keep each one working.
surfaceThe route and HTTP method, or the MCP tool.Which part was used.
argumentsEvery argument, stored up to 2,048 characters: the name or domain, record type, resolver, transport, address family, flags, client subnet, a resolver address you typed. Refused names too.What was asked, to fix wrong or missing readings and refusals.
refusalWhy a request was refused: special-use name, name inside a network, private address, resolver not on the board, bad argument, limited, or failed.To see which refusals are wrong.
outcomeThe HTTP status, the tool's outcome, the DNS response code, and a domain check's ok, warn and fail counts.What result the service reported, to look into wrong or failed readings.
latencyTime to answer, in milliseconds.How fast it answered.
locationThe Cloudflare data center the request entered, and its country.To read latency and vantage.

Two example records from test lookups. The addresses are documentation addresses (RFC 5737, RFC 3849). ts is Unix time in milliseconds.

An MCP call that worked: dig example.com A. No address, no user agent.

POST https://isitdns.net/mcp  from 192.0.2.10
tools/call dig {"name":"example.com","type":"A"}

request row:
ts          1791813600008
name        "example.com"
qtype       "A"
resolver    "cloudflare"
transport   "doh"
ip_family   "v4"
flags       "dnssec"
ecs         NULL
custom_ip   NULL
country     "NL"
colo        "AMS"
source      "auto"
rcode       "NOERROR"
latency_ms  6
ua          NULL
ip          NULL
refusal     NULL
argv        "{\"name\":\"example.com\",\"type\":\"A\",\"dnssec\":true,\"cd\":false,\"noRecurse\":false,\"nsid\":false,\"transport\":\"doh\",\"ipFamily\":\"v4\",\"resolver\":\"cloudflare\"}"

MCP row:
ts       1791813600010
class    "other"
tool     "dig"
name     "example.com"
args     "A @cloudflare"
outcome  "ok:NOERROR"
ms       10
colo     "AMS"
country  "NL"
ip       NULL
ua       NULL
refusal  NULL
argv     "{\"name\":\"example.com\",\"type\":\"A\"}"

A request that was refused: /dig for nonexistent.invalid, a special-use name. The address and user agent are kept.

POST https://isitdns.net/api/query  from 2001:db8::10
{"name":"nonexistent.invalid","type":"A","resolver":"cloudflare","dnssec":true,"cd":false,"transport":"doh"}

request row:
ts          1791813600014
name        "nonexistent.invalid"
qtype       "A"
resolver    "cloudflare"
transport   "doh"
ip_family   "v4"
flags       "dnssec"
ecs         NULL
custom_ip   NULL
country     "NL"
colo        "AMS"
source      "site"
rcode       NULL
latency_ms  1
ua          "Mozilla/5.0 (example browser)"
ip          "2001:db8::10"
refusal     "special-use"
argv        "{\"name\":\"nonexistent.invalid\",\"type\":\"A\",\"resolver\":\"cloudflare\",\"dnssec\":true,\"cd\":false,\"transport\":\"doh\"}"

Values: source "auto" = MCP, "site" = the /dig page. class "other" = a client type that is not one of ours. flags "dnssec" = the DO bit set.

Other data:

  • Web pages: Cloudflare's beacon counts page views. No cookies. No accounts. No ads. Opening a page writes no log row, including a page that does not exist. The /top100, /top-100, /status.txt and isitdns.net/<domain> redirects write one row, with no address. A lookup the page runs does.
  • MCP counts at Cloudflare contain the method, tool, client type, outcome and latency, and for a failed or refused call the first 80 characters of the user agent after email addresses are removed. They contain no IP address. Counts written before this change, which went live on 2026-10-13 UTC, carry that part of the user agent for every call; each expires three months after it was written, the last by 2027-01-13.
  • Rate limit: a hash of your IP address and a count, per minute. For the path tests, your address is held only in the server's memory, is never written, and is dropped when the next minute's count starts. Only a count per route is written, with no address.
  • Dig reader compare (/api/compare): one row per question it answers or refuses, with the time, the HTTP status, the refusal category and the latency. The row has no name, no record type, no IP address and no user agent, whether the request worked, failed or was refused: the count is all the service needs from that door. A paste into the dig reader stays in your browser.
  • Network diagnosis and path receipt (/api/diagnose, /api/path-receipt): one row per request, with the time, the route, the HTTP method, the HTTP status, the refusal category and the latency. The row has no name, no test name, no argument, no IP address and no user agent, whether the request worked, failed or was refused.
  • Feedback and question endpoints (/api/feedback, /api/inquiry): what you send, your country as recorded for that request, and a hash of your IP address that changes daily.
  • Probe signup list: email addresses, an optional note, your country as recorded for that request, and a hash of your IP address that changes daily.
  • Tests (/api/tests): the test as you wrote it (its name, the hostname, record type, server, transport, expected answers, period, window and vantages), when it was created, a hash of the owner token, a hash of your IP address (or its /48) that changes daily, and the day its page was last opened; each reading (vantage, time, the address or DoH host and the transport asked, rcode, flags, latency, answers, its label, the control's reading, an error), with no address of yours and no user agent.
  • Probe reports (/api/hive/report): a probe's own summary of its DNS traffic (counts, latency, top names), its country and network number. No resolver address.
  • Traffic counts copied from Cloudflare: visits and page views per window, the top 10 pages, countries, browsers and operating systems by page views, and the site's request, byte, cache, threat and error counts. Counts only, with no address, kept 2 days. /api/metrics publishes the newest copy.
  • Tool outputs: a check_domain answer is cached 5 minutes in the Cloudflare data center that ran it and served to the next caller there who checks that domain. dig, trace, dnssec_chain, sweep_domain and registration answers are returned to the caller only. Resolver readings and monitored-domain snapshots are measurements of public DNS, used for the status board and its history. They hold no visitor data.
  • DNS: Cloudflare answers the isitdns.net zone, and isitdns receives no record of those queries. isitdns's own name servers answer probe.isitdns.net (the canary, who, whoami and the test names) and write nothing per query: no address, no name, no line per error. They count queries per hour, by record type, transport and response code class. After an hour ends, that hour's count line is written, one per zone. Internal errors are counted every five minutes. A path receipt's arrivals (the address that asked and how it asked) are held in the name server's memory for 10 minutes, for the receipt to read, and are never written.
how long it is kept

When it works, isitdns does not keep who asked. Failed or refused requests keep the address and user agent 30 days, so they can be traced. Request logs are deleted at 30 days.

Path tests are the exception: a failed or refused one keeps no address and no user agent either.

Separate MCP usage counts keep up to 80 characters of a failed or refused call's user agent, after email addresses are removed, for three months. The rate limit keeps a hash of the address for up to a day.

  • Request log rows: 30 days.
  • A second copy of the dig, MCP and API rows, for the operator dashboards: 15 days.
  • Backups: deleted rows stay in Cloudflare database backups up to 30 more days.
  • Counts, with no address: requests a day by tool and client type, digs by resolver and record type. Kept with no set end.
  • MCP count points at Cloudflare: three months.
  • Page-view counts at Cloudflare: six months.
  • Traffic counts copied from Cloudflare: 2 days.
  • Resolver readings: raw readings up to 2 days, 5-minute summaries 30 days, hourly summaries 90 days, daily summaries with no set end.
  • Monitored-domain snapshots: one per domain per day, with no set end.
  • Rate limit entries: deleted within a day.
  • Name server counts: the current and the last hour in memory; the hourly count lines, 30 days. Lines written before this change are deleted at 30 days.
  • Test readings: 30 days; a test's history keeps a copy of the first reading that missed for as long as the test lives. A test whose page nobody opens for 30 days is removed, with its readings and its history.
  • Feedback, questions, probe signups and probe reports: kept while isitdns runs, to answer them and keep each probe's history; deleted on request.
  • Email to isitdns: no scheduled deletion date; deleted on request.
what gets used

not read yet

doorlast 30 daystotalby day
recipients
  • Cloudflare: every request passes through it. It hosts the site, the API, the database and the page-view counts. Cloudflare's privacy policy.
  • Hosting and network providers carry each probe's and name server's traffic. A lookup run from a probe passes through that probe's hosting provider.
  • The DNS servers a lookup asks receive the name, the type, and a client subnet if you send one. RDAP servers receive the domain name. isitdns does not add your IP address; a DNS server receives a client subnet only if you supply one.
  • Email to isitdns goes to Apple iCloud Mail.
  • Not sold. Not shared for advertising. The one third-party script is Cloudflare's page-view beacon.
your controls

No accounts.

To see or delete your data, write to security@isitdns.net. Answered within 30 days.

  • Request log rows: give the IP address and the time window (UTC). A lookup by IP finds only failed or refused requests; a request that worked has no address to find in the request log.
  • Feedback and questions: give the IP address and the day, or the text or email address you sent.
  • Probe signups: give the email address.
  • Probe reports: give the probe's id.

You get the rows found, or they are deleted from active storage, and the reply says which. Deleted rows remain in Cloudflare backups for 30 days. The second copy is not reached by a deletion; it expires within 15 days.

changes

Changes are dated below.

Last changed: 2026-11-04.