Fast at the edge
A resident in-memory lookup path keeps common requests quick, while the public API stays simple enough to call from any stack with one HTTP request.
Built from public internet data sources
ARINRIPE NCCAPNICLACNICAFRINICBGPGeoNamesRFC 8805
Features
Why build with the ip-api.dev API?
One request, transparent inputs, and useful network context beyond a pin on a map.
Powerful and simple
One response combines geolocation, BGP routing, registry ownership, reverse DNS and network risk signals. No SDK or local database is required.
Auditable data
Location precision and provenance are explicit. Results are assembled from operator geofeeds, RIR allocations, routing tables and published provider ranges.
Global IPv4 and IPv6
Look up public IPv4 and IPv6 addresses, inspect the covering prefix, and move through the allocation hierarchy from a single consistent interface.
Free for small projects
Start with 100 keyless requests per day or create a free account for 1,000. Upgrade only when your traffic and feature needs grow.
Threat and service signals
Typed flags identify datacenters, VPNs, proxies, Tor exits, abusive networks, crawlers and mobile carriers.
Use cases
Network context for every IP address
Make routing, personalization and risk decisions with evidence your team can inspect.
Location with provenance
Personalize content without pretending IP geolocation is more precise than it is. Every answer describes its geographic precision and the source behind it, whether that is an operator-published geofeed or a registry allocation. Use country, region, city, coordinates and time zone only when the evidence supports them.
curl 'https://ip-api.dev/api?q=8.8.8.8'
{
...
"country": "United States", "country_code": "US", "precision": "country", "basis": "registry_allocation", "latitude": 37.386, ...
}BGP routing and ASNs
See the autonomous system that originates the most specific route covering an address, including the announced prefix, organization, registry and network type. Query an AS number directly when you need its active IPv4 and IPv6 prefixes for routing analysis, allowlists or infrastructure inventory.
curl 'https://ip-api.dev/api?q=1.1.1.1'
{
...
"asn.number": 13335, "asn.name": "Cloudflare, Inc.", "asn.route": "1.1.1.0/24", "asn.type": "hosting", "asn.active": true, ...
}Registry ownership
Trace an address to the registered network and organization that holds it. The response includes the covering allocation, RIR, country, organization domain and published abuse contact, giving support and security teams useful ownership context without a separate whois integration.
curl 'https://ip-api.dev/api?q=9.9.9.9'
{
...
"network.cidr": "9.9.9.0/24", "network.rir": "arin", "organization": "Quad9", "domain": "quad9.net", "country_code": "US", ...
}Proxy, VPN and threat context
Add network context to fraud rules and access decisions. Typed flags identify hosting ranges, VPN providers, proxies, Tor exits, abusive networks and known crawlers, while service records explain the provider, role, confidence and last-seen time behind a positive signal.
curl 'https://ip-api.dev/api?q=8.8.8.8'
{
...
"is_datacenter": true, "is_proxy": false, "is_vpn": false, "is_tor": false, "is_abuser": false, ...
}Data lineage
IP intelligence you can audit
Open inputs and explicit provenance make every result easier to understand and verify.
Published at the source
Network operatorsOperator geofeeds and published cloud ranges provide direct evidence for location and infrastructure classifications.
Mapped to live routing
Open routing dataBGP announcements connect each address to the active route and autonomous system visible on the public internet.
Refreshed continuously
Scheduled datasetsEvery source has freshness tracking and a defined refresh schedule, so stale or delayed feeds are visible instead of hidden.
FAQ
FAQ about the IP Intelligence API
The common questions developers ask before making their first request.
What does the API return?
A single lookup can return location, ASN and BGP route, registered network, organization, abuse contact, hostname and network risk flags.
How accurate is IP location?
Accuracy depends on the available evidence. The API reports a precision and basis so your product can distinguish city-level geofeeds from country-level registry data.
Do I need an API key?
No key is needed for the first 100 requests each day. A free account raises the limit and unlocks the complete response body.
Can I query an AS number?
Yes. Query values such as AS13335 return autonomous-system details and the active IPv4 and IPv6 prefixes announced by that network.
Which formats are supported?
JSON is the default. The same lookup is also available as CSV, plain text and HTML, and bulk requests accept up to 1,000 addresses.
Can I use it commercially?
Yes. Free and paid plans can be used in commercial products. Paid tiers add higher daily limits and larger bulk workloads.