Open data · CC BY 4.0 · version 2026-09-24

Public DNS resolver dataset

One row per documented resolver address, with the operator, variant, filtering description, encrypted endpoints and our measurements. Free to use with attribution.
167
address rows
20
operators
265
facts checked against sources
16
columns

Method

How the data was collected

Addresses, DoH URLs, DoT hostnames and filtering descriptions are copied from each operator’s documentation and checked word for word against the rendered page. Every documented IPv4 address was queried three times from one vantage point: DNSSEC by three deliberately mis-signed domains, ECS by the subnet echoed at o-o.myaddr.l.google.com, and NXDOMAIN by a random .com name. DoH was tested over HTTP/2 and DoT on port 853 with certificate validation. Announcing prefixes and ASNs come from RIPEstat.

Reading the measurement columns

  • dnssec_validates: true when all three mis-signed names returned SERVFAIL, false when all three resolved, empty otherwise.
  • ecs_prefix_sent: the prefix length the authoritative server received; 0 means none.
  • nxdomain_returned: true when a random non-existent name returned NXDOMAIN.
  • IPv6 rows carry documentation only; they were not probed.

Limits

  • One vantage point on 2026-09-24. Anycast resolvers can route and behave differently elsewhere.
  • Speed, uptime and filter effectiveness are not measured.
  • Operator policies are quoted on each registry page, not verified.
  • Sources checked 2026-09-24; operators can change addresses later.

Schema

Columns

operator_slugoperatorservicevariantfilteringaddressip_versionanswered_plain_dnsdnssec_validatesnxdomain_returnedecs_prefix_sentannouncing_prefixannouncing_asnsdoh_urlsdot_hostsdocumentation

License

License and citation

Our compilation and measurements are available under CC BY 4.0. Credit PROXIES.SX and link to this page. Operator names and trademarks belong to their owners.

PROXIES.SX. (2026-09-24). Public DNS Resolver Registry. https://www.proxies.sx/dns-resolvers/dataset

Browse the data by resolver on the DNS resolver registry.