DNS.Watch answers on 84.200.69.80 and 84.200.70.40 and promises uncensored, unlogged DNS with DNSSEC validation. It has run since 2014, but its site has not been updated since 2019 and its DNS over HTTPS no longer works — in a test on 27 September 2026 the second address answered reliably, the first only some of the time.
| Service | Addresses |
|---|---|
| DNS.Watch | 84.200.69.8084.200.70.402001:2001: |
| Run by | DNS.Watch (not named on its site) |
| Validates DNSSEC | Yes — a record whose signature fails validation is not returned |
| Sends your subnet (ECS) | Not documented |
| Blocks | Nothing — “uncensored records” |
| Logs | No query logs |
What does DNS.Watch answer for your domain?
Enter a hostname: we ask DNS.Watch and the domain’s own nameservers, and show whether its cached copy is up to date — and if not, how long until it asks again.
What it logs
“All our resolvers are setup to not log any queries”; anonymised data not linked to users is used for statistics and security research.
Worth knowing
- Its site says its DNS over HTTPS and DNSCrypt are “Currently NOT working”, and the DoH hostname it shows no longer exists.
Sources
Checked on 27 September 2026 against these official sources:
- DNS.WATCH — dns.watch
- DNS.WATCH: why use it — dns.watch