Trusted IP intelligence database licensing.
We measure the internet and license the result as databases you download: geolocation, anonymity, ownership, network and service data for IP addresses and AS numbers, and every registered gTLD domain. Trusted by the largest IP intelligence vendors to power their own data and products.
| start_ip | end_ip | provider | confidence | last_seen |
|---|---|---|---|---|
| 216.131.87.112 | 216.131.87.127 | ipvanish | high | 2026-09-08 |
| 208.85.18.71 | 208.85.18.71 | tunnelbear | high | 2026-09-07 |
| 187.13.129.184 | 187.13.129.187 | nordvpn | high | 2026-09-07 |
| 172.235.240.0 | 172.235.240.11 | metrovpn_net | medium | 2026-09-04 |
| 95.170.13.20 | 95.170.13.23 | pingvpn_pingsecure | low | 2026-06-16 |
Look up any address, range, network or country.
Every database answers for one address: where it is, who announces and registered it, whether it hides someone, and what answers on it. Ranges, AS numbers and countries open their own pages of networks, prefixes and providers.
Which providers we track.
All major VPN and proxy providers, covered deeply.
NordVPN
Proton VPN
ExpressVPN
Surfshark
Mullvad
CyberGhost
Private Internet Access
Windscribe
IPVanish
TunnelBear
hide.me
PureVPN
Hotspot Shield
VyprVPN
Mozilla VPN
Norton VPN
Psiphon
Bright Data
Oxylabs
Decodo
IPRoyal
SOAX
Webshare
Rayobyte
DataImpulse
Proxy-Cheap
PacketStream
Infatica
ProxyEmpire
Massive
Shifter
ZyteEvery record behind an address.
The registries, operators' own RWHOIS servers, the routing table and our own scans, resolved to the address.
- Used byAPNIC and Cloudflare DNS Resolver project · cloudflare.comHostingIP Company
- Announced byAS13335 Cloudflare, Inc. · 1.1.1.0/24RPKI validIP ASN
- AS recordCLOUDFLARENET · ARINASN Whois
- Registered toAPNIC Research and Development · APNIC-LABS · APNICIP Whois
- Reassigned toNo reassignment publishedIP RWHOIS
- Abuse contacthelpdesk@apnic.netIP Abuse Contact
- Reverse DNSone.one.one.oneIP RDNS
What kind of network it is.
Mobile carrier space with its MCC and MNC, anycast ranges and CDN edge space, each told apart.
Every address, placed on the map.
Continent, country, region and city for every range, with the city's timezone and postal code, and an accuracy radius for each.
What every address runs.
The SSH, mail and web servers that answer on the open internet, with their banners, certificates and fingerprints, and every DNS resolver, from our own measurement.
Every registered domain, and its DNS.
Each domain registered under the generic top-level domains, one name per row, and the A, AAAA, MX, NS and CNAME records domains resolve to, a file per record type.
Download it in four calls.
Official clients wrap the download API: fetch the current build and the digests to verify it against, then query it locally. No request per address, no lookup service in your path.
database.list()database.metadata(id)database.download(id, fmt, path)database.checksums(id, fmt)import osfrom internetdata import InternetDataclient = InternetData(os.environ["INTERNETDATA_API_KEY"])# what is in today's build, without moving the filemeta = client.database.metadata("vpn_ip_v1")client.database.download("vpn_ip_v1", "mmdb", "./vpn_ip_v1.mmdb")sums = client.database.checksums("vpn_ip_v1", "mmdb")print(meta.updated, meta.entries, sums["sha256"])
Simple licensing terms, pick your database.
Full licensing detail →Use the data inside your own product, service and operations, with no metering.
Resell it forward in your own product, even directly as a database, or to power your IP data API.
Is there a lookup API?
No. You run the databases where your traffic already is, so there's no round trip, rate limit or per-query bill, and your customers' addresses never leave your infrastructure. Builds arrive through the database API: list, metadata, download, checksum.
How often is the data rebuilt?
Daily for most databases, and weekly for IP RDNS, IP RWHOIS, Domain List, Domain DNS and the four port scans (SSH IP, SMTP IP, Web IP and DNS Resolver IP). Ask /api/v2/database/metadata before you fetch and it answers updated and entries, so a build is only pulled when it is worth pulling.
Can we resell or embed the data?
Yes, under a redistribution license. Your license type shows against every database in the console: evaluation, standard or redistribute.
Can we see the data before we commit?
Yes. An evaluation license is for internal testing, runs for a fixed period under NDA, and converts into whichever license fits.
Who else licenses these databases?
Several of the largest IP-intelligence vendors ship our anonymity data inside their own products. Their contracts keep the names out of public material; under NDA we are specific about who, which datasets and since when.
What happens when a classification is wrong?
Send the address and what you observed. Corrections are investigated against the raw observations and, where we agree, land in the next daily build, and we tell you which build carries the change.
Test the real build first.
An evaluation license puts a full current build in your hands, with no sampling, so you can measure it against your own traffic before anyone talks about terms.