Every DNS resolver answering on the open internet.
Each address answering DNS on UDP port 53, with whether it advertises recursion and whether it really resolves a query: the two marks of an open resolver, which reflection attacks abuse.
In the lookup API: is_dns_resolver on every plan, and dns_resolver on a paid plan.
Real rows, with what each column means.
See documentation →The schema and metadata are in the docs. It is published as CSVGZ.
| ip | port | recursion_available | rcode | answer_correct | first_seen | last_seen |
|---|---|---|---|---|---|---|
| 2.133.114.39 | 53 | 1 | 0 | 1 | 2026-07-06 | 2026-07-14 |
| 31.131.30.165 | 53 | 5 | 2026-07-07 | 2026-09-25 | ||
| 97.107.134.164 | 53 | 1 | 0 | 2026-07-06 | 2026-09-30 | |
| 81.0.236.73 | 53 | 2 | 2026-07-10 | 2026-09-25 | ||
| 60.187.245.11 | 53 | 0 | 1 | 2026-08-27 | 2026-09-14 |
Download it from your code in one call.
Database API reference →Every official client fetches the current DNS Resolver IP build to disk, as a link for your own runner or into memory, and checks it against its published checksums.
download()downloadUrl()downloadBytes()metadata()checksums()import osfrom internetdata import InternetDataclient = InternetData(os.environ["INTERNETDATA_API_KEY"])# what is in today's build, without moving the filemeta = client.database.metadata("dns_resolver_ip_v1")client.database.download("dns_resolver_ip_v1", "csvgz", "./dns_resolver_ip_v1.csv.gz")sums = client.database.checksums("dns_resolver_ip_v1", "csvgz")print(meta.updated, meta.entries, sums["sha256"])
Most of it sits in these countries and networks.
DNS Resolver IP holds 6,702,416 IPv4 addresses in the latest build. These are the countries and networks with the most of them; each opens its own page, as does every IP range.
By country
Of the 6,702,416 IP Geolocation places.
By network
Each /24 counted for the AS announcing most of it.
- AS58224Iran Telecommunication Company PJS493,035 · 7.36%
- AS8048CANTV Servicios, Venezuela181,449 · 2.71%
- AS16276OVH SAS176,304 · 2.63%
- AS19551Incapsula Inc171,516 · 2.56%
- AS36947Telecom Algeria160,990 · 2.40%
- AS3462Data Communication Business Group122,666 · 1.83%
- AS31898Oracle Corporation122,248 · 1.82%
- AS4134CHINANET-BACKBONE110,345 · 1.65%
- AS12389PJSC Rostelecom101,451 · 1.51%
- AS4837CHINA UNICOM China169 Backbone96,547 · 1.44%
Put it to work in your own systems.
Teams join DNS Resolver IP against traffic they already log, inside their own infrastructure, and never send an address anywhere to get an answer.
Reflection-attack defense
Identify open recursive resolvers that can be abused for DNS reflection and amplification.
Address-space hygiene
Audit your own ranges for resolvers that answer the open internet when they should not.
Risk scoring
Separate ordinary name servers from resolvers that recurse for anyone, using the recursion and answer flags.
Call the API in your language, with an official client.
All SDKs on GitHub →Thirteen official clients, one for each language you ship in and one for the browser, plus middleware for seven web frameworks. Each answers private addresses without a request, caches what it looks up and splits big batches for you.
Common questions
What separates an open resolver from a name server?
recursion_available says the server advertises recursion; answer_correct says it resolved a known name to the right address. A server with both is a working open resolver. One that advertises recursion and answers REFUSED isn't.
What do the rcode values mean?
The DNS response code: 0 is NOERROR, 2 SERVFAIL and 5 REFUSED. With recursion_available it separates a true open resolver from one that refuses outside queries.
Why does answer_correct matter?
A resolver that answers a known name with the wrong address is changing answers, by filtering, redirecting or hijacking them. Only a correct answer counts as a working open resolver.
Why are open resolvers a problem?
They answer anyone, which lets an attacker send queries with a victim's address as the source and have the amplified replies land on the victim.
How often is it rebuilt?
Weekly over a rolling 90-day window, which first_seen and last_seen are relative to. The metadata call answers when the current build landed and how many rows it holds, before you fetch it.
Which formats does a build ship in?
Gzipped CSV. Each row is one address, so a prefix tree would not make it smaller.
How do we get it?
Under a Standard or Redistribution license, quoted per database. Get a quote names DNS Resolver IP to us, and Request evaluation puts the full current build in your hands to test first. Download sample gets you rows from it now.
Is there a lookup API?
Yes. An address lookup answers is_dns_resolver on every plan, free included, and dns_resolver on a paid plan.
What if a row looks wrong?
Send it to us and we'll tell you what we hold on it and when it was last seen. Corrections land in the next build.
Unlimited lookups, no sign-up.
Paste it into a terminal. Any address answers with its country, network, company and hostname, with no key and no daily or monthly cap. ASes and domains answer too.
{"ip": "8.8.8.8","is_bogon": false,"is_tor": false,"is_relay": false,"is_anycast": true,"is_carrier": false,"is_satellite": false,"is_ssh": false,"is_smtp": false,"is_web": true,"is_dns_resolver": true,"is_bittorrent": false,"hostname": "dns.google","location": {"continent": "NA","continent_name": "North America","country": "US","country_name": "United States","timezone": "America/Los_Angeles","currency_code": "USD","currency_name": "Dollar","currency_symbol": "$","flag_emoji": "🇺🇸","flag_unicode": "U+1F1FA U+1F1F8"},"asn": {"asn": 15169,"name": "Google LLC","domain": "google.com","type": "hosting","prefix": "8.8.8.0/24"},"company": {"name": "Google LLC","domain": "google.com"},"tor": {},"relay": {},"abuse": {"email": "network-abuse@google.com"}}
All of the data on a paid plan.
A free API key answers every field for its first 100 lookups each day, with no card.