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

The isitdns protocol

the isitdns protocol

what:The isitdns protocol is a set of DNS names under isitdns.net that answer "is it DNS?" with records anyone can read with dig.

halves:The read surface carries the monitor's verdict as TXT records (help and isit also carry an A); the report channel answers with what reached isitdns's own name servers.

version:version 2.1, first published 2026-10-30, surface 8

author:Neal Shelton

uses
usediglabel
before blaming DNSdig +short isit.isitdns.net TXTthe verdict, stamped
which resolver reached usdig +short whoami.probe.isitdns.net TXTthe address of the resolver that asked
whose network askeddig +short who.probe.isitdns.net A192.0.2.1 Cloudflare, 192.0.2.8 Google Public DNS, 192.0.2.99 any other network
answered in our place?dig +short canary.probe.isitdns.net A192.0.2.111, or not; a match does not say the path was clean
root key roll readinessdig +short ksk.isitdns.net TXTthe public resolvers, counted by how they handle the root key
scripts and AI agentsany read-surface nameDNSSEC-signed, no web page
1. the read surface

The read surface is eight names directly under isitdns.net, and a version record at _isitdns, whose TXT records (and the A records of help and isit) carry the verdict the site shows, stamped with the time of its newest reading.

1 you dig isit.isitdns.net TXT 2 any resolver yours, 1.1.1.1, 8.8.8.8 ... 3 isitdns.net name servers the zone holds the verdict 4 TXT + A the verdict, stamped
The read surface: your dig goes to any resolver, the resolver asks the isitdns.net name servers, and the TXT and A verdict comes back to you.
  • helpthe verdict sentence, the menu of names, the receipt line, the tokens; A: the word as a code
  • isitthe tokens, then the word; A: the word as a code
  • whyeach resolver that is not ok, or "all measured resolvers answering"
  • kskthe root key roll board: which public resolvers trust which root key
  • cloudflarethat resolver's line: status, latency, DNSSEC, then one string per address family and transport
  • googlethe same, for Google Public DNS
  • quad9the same, for Quad9
  • adguardthe same, for AdGuard DNS
  • _isitdnsthe version record: v=isit1 surface=8 round=180 spec=https://isitdns.net/wiki/dig/ask-dns

Every name is <name>.isitdns.net, one TXT each, TTL 60 s; the version record caches longer. The zone is DNSSEC-signed. Every line describes isitdns's own probes, never your network; the help record's receipt line says so: "probe: ours not yours".

2. records and fields

Each record is one or more strings; the fields below are what isit and the last string of help carry.

  • stateok, degraded, failing or stale: the word as a token
  • badresolvers failing from every probe that read them
  • measuredresolvers with a verdict
  • probesprobes the verdict was read from; 0 when nothing was measured
  • seatsthe same count under its old name, served beside probes at surface 8
  • asofthe newest reading behind the line, UTC, to the second; not the time the record was written

The word, and its code in the A record of help and isit:

  • 127.0.0.2no (state=ok): no measured resolver is struggling
  • 127.0.0.3mostly (state=degraded): some resolvers are struggling
  • 127.0.0.4maybe (state=failing): half or more are down
  • 127.0.0.5no data (state=stale): no verdict

127.0.0.1 is never one of these codes. The addresses are loopback so a code is never a host to connect to (RFC 5782 section 2.1).

3. one real answer

One question to isit.isitdns.net over DoH, and what came back, piece by piece.

$ dig +https @cloudflare-dns.com +short isit.isitdns.net TXT

"state=ok bad=0 measured=16 probes=3 seats=3 asof=2026-10-30T16:21:01Z" "no"

2026-10-30 16:24:33Z, a machine asking cloudflare-dns.com over DoH.

  • state=okthe word as a token: no
  • bad=0no resolver failing everywhere
  • measured=1616 resolvers with a verdict
  • probes=3read from 3 probes
  • seats=3the same count, old name
  • asof=2026-10-30T16:21:01Zthe newest reading, 212 s before the question
  • "no"the word, the second string

$ dig +https @cloudflare-dns.com +short isit.isitdns.net A

127.0.0.2

2026-10-30 16:24:34Z, a machine asking cloudflare-dns.com over DoH.

  • 127.0.0.2the code for no; read only beside a live TXT

$ dig +https @cloudflare-dns.com +short _isitdns.isitdns.net TXT

"v=isit1 surface=8 round=180 spec=https://isitdns.net/wiki/dig/ask-dns"

2026-10-30 16:24:34Z, a machine asking cloudflare-dns.com over DoH.

  • surface=8the version of the names and grammar on this page
  • round=180the shortest time between two changes to the zone, in seconds

label:live at capture, no

The same question from any machine, through its own resolver: dig +short isit.isitdns.net TXT.

4. client rules

A client is any program that turns these records into a verdict; these are the rules it follows.

  1. A client MUST join the strings of one record with nothing between them (as RFC 7208 section 3.3 does for multi-string TXT). In help each part is found by its prefix: is it DNS? , ask: , receipt: , state=.
  2. A stamp is live when -180 <= age < 600 seconds, age being the client's UTC clock minus the stamp; 1200 in place of 600 for ksk. A stamp that is not live is no data, whatever the word beside it says.
  3. The TXT wins. An A answer beside a TXT that is not live, or beside no TXT, is no data. A client MUST NOT connect to a code address, and MUST treat 127.0.0.1 or an address outside the four codes as not this protocol.
  4. A token line without state or asof, or with a key twice, is not usable. Unknown keys MUST be ignored. A word and a state that disagree are no reading.
  5. SERVFAIL, a timeout, REFUSED, NXDOMAIN, or NOERROR with no record for one of these names is no reading, never a verdict. More than one TXT, or more than one A, at one name is no reading.
  6. A surface the client does not implement, or a version record that does not open with v=isit1, MUST NOT be turned into a verdict, and MUST NOT be reported as a DNS outage.
  7. A client SHOULD validate the answer itself, or accept the AD bit only from a validating resolver it trusts over a secure channel (RFC 4035 section 4.9.3). A bogus answer MUST NOT be read as a verdict.

The grammar of every record, and a reader that uses exactly these bounds: asking DNS about isitdns.

5. the report channel

The report channel is three names under probe.isitdns.net whose answer is made from the query that reached isitdns's own name servers.

1 you dig who.probe.isitdns.net 2 your resolver asks on your behalf 3 isitdns name servers read the address that asked 4 A + TXT what reached us
The report channel: your resolver carries your query to the probe.isitdns.net name servers, which answer with what reached them: the address the query came from and whose network it is.
  • canaryA 192.0.2.111, exactly; any other answer came from something answering in its place, or the zone was changed
  • whoA 192.0.2.1: the query came from Cloudflare's network; 192.0.2.8: from Google Public DNS's; 192.0.2.99: from a network with no published list. TXT src=<address> via=<cloudflare, google or none>
  • whoamiTXT: the address the query came from

Each is <name>.probe.isitdns.net, DNSSEC-signed; who and whoami answer with TTL 0, so every query is read fresh. The addresses are documentation addresses (RFC 5737). A match says the query reached us from that network; it does not say the path was clean.

Two legs. Leg one is your device to its resolver, over port 53, DoT on port 853 or DoH on port 443, whichever your device is set to (RFC 1035 section 4.2, RFC 7858, RFC 8484). Leg two is the resolver asking isitdns's name servers, and it is the leg the report channel reads: it arrives on port 53, over UDP or TCP (RFC 7766 section 5), from the resolver's own address, whatever leg one was. So a device on DoT or DoH still gets a reading, and the address in it is its resolver's, not the device's.

What reaches the name servers. The address the question came from and the question with its flags; the network an address belongs to is looked up from the address. Not how your device reached its resolver, not your device's name, and not its address, except that some resolvers add a shortened client subnet (ECS, RFC 7871), which the answers here do not use.

The check-in. The path test (/tools/test-your-own-path) makes a fresh name and has you ask it once, so what arrives is your resolver's question and not a cache's answer. It reads back each arrival: which name server it reached, the address it came from, UDP or TCP, the RD, DO and CD bits, the EDNS buffer size, and the ECS prefix lengths, never the subnet itself.

$ dig +tls @1.1.1.1 +short whoami.probe.isitdns.net TXT

"104.22.26.111"

2026-11-03 11:55:05Z, a machine asking 1.1.1.1 over DoT.

label:Cloudflare's address, not the machine's

$ dig +https @cloudflare-dns.com +short who.probe.isitdns.net A

192.0.2.1

2026-10-30 16:24:34Z, a machine asking cloudflare-dns.com over DoH.

label:from Cloudflare's network

$ dig +https @cloudflare-dns.com +short who.probe.isitdns.net TXT

"src=172.71.29.237 via=cloudflare"

2026-10-30 16:24:34Z, a machine asking cloudflare-dns.com over DoH.

label:172.71.29.237, Cloudflare

$ dig +https @cloudflare-dns.com +short canary.probe.isitdns.net A

192.0.2.111

2026-10-30 16:24:34Z, a machine asking cloudflare-dns.com over DoH.

label:the reference answer

Not running today: the beacon, sessions, and a read-back of the transport and flags inside the answers of these three names (the path test reads them back for its own fresh names).

6. what isitdns keeps

What a query to these names or a request to the site leaves with isitdns, every field and for how long, is on one page: /privacy.

7. version and source

This page is version 2.1 of the isitdns protocol, read surface 8, published from spec 2.1-draft at the commit below.

  • published2026-10-30, first
  • surface8, as _isitdns.isitdns.net serves it
  • spec commit32ad1fb7931aa5f344cbe7a25bf8fa979128ea1b
  • byNeal Shelton
8. what changed

Changes to the names, records and fields on this page, newest first. From 2026-10-14.

The read surface is surface 8, since 2026-10-06.

  • 2026-10-30 · #404 · The protocol is published at /protocol, version 2.1.
  • 2026-10-28 · #356 · The _isitdns record's spec= points to /wiki/dig/ask-dns.
  • 2026-10-27 · #348 · who.probe.isitdns.net answers with the network of the resolver that asked.