Get started
Look up an IP address, an AS or a domain in one call with no key, then pick a path: an SDK, a web app's middleware, the databases or no code.
On this page
InternetData answers what is known about an IP address, an AS or a domain: where an address is, the network and company behind it, whether it is a VPN, proxy, Tor exit or hosting server, and its registry records. The quickest way to see it is one call with no account:
curl https://api.internetdata.io/8.8.8.8{
"ip": "8.8.8.8",
"is_anycast": true,
"is_dns_resolver": true,
"location": { "country": "US", "country_name": "United States" },
"asn": { "asn": 15169, "name": "Google LLC", "type": "hosting" },
"company": { "name": "Google LLC", "domain": "google.com" },
"hostname": "dns.google"
}Your first lookup walks through that answer and adds a key.
Pick your path
- Use an SDK: look addresses, ASes and domains up from your own code.
- Add it to a web app: middleware looks up every visitor, for you to personalize, review or refuse.
- Use the databases: download a file and look addresses up on your own servers.
- Without code: the CLI, the browser extension, AI assistants, plugins and BigQuery.
Before you ship
- Going to production: keys, timeouts, retries, caching and usage.
- Plans and fields: what the free plan answers, and why a field can be absent.
- The visitor's address: behind a proxy or a CDN, look up the right one.
- Caching and cost: what to cache, and for how long.
- API or database: which one suits your traffic.
Something specific to build? The guides take one job each, start to finish.