Is it DNS? Find out in two queries.
No install. No agent. Nothing phones home. Paste two ordinary DNS queries into any terminal you already have. The queries are the diagnosis — you read the answer yourself. Works on a laptop, a server, a container, a router shell: anywhere DNS resolves.
Run it right here, over DoH
One click. Your browser mints a fresh nonce and asks over DNS-over-HTTPS (RFC 8484). Nothing is stored; the query goes to a public resolver, same as any page load.
Or paste it into any terminal
1 · Is your DNS answer being rewritten?
Ask for the public tripwire name. Its answer is a fixed test address
(192.0.2.111, reserved and unroutable). If you get anything else back, something on
your path rewrote the answer.
good: 192.0.2.111 · anything else: your DNS answer was rewritten in flight
2 · Did your query reach the genuine authority?
Ask for a name that has never existed and never will — a fresh random label. No cache, forwarder, or interceptor can have an answer ready, so a reply means your query actually reached a real authority. The reply is a signed receipt (verify it with the one-file probe if you want proof, not just a signal).
good: a base64url TXT string comes back · empty / SERVFAIL: your path never reached the authority
dig always has. Nothing is installed and
nothing reports back about you. For cryptographic proof (verify the signature, see the resolver
exit the authority saw), run the keyless one-file probe — still no daemon, no inbound ports.
Want proof, not just a signal?
One file, no root, no daemon, deletes clean. It runs the same idea over plain DNS, DoT, and DoH, and verifies the signature for you: