Skip to content
API Guides

Best IP Data Service: How to Choose an IP Intelligence API

How to choose the best IP data service: full data on every plan, verified VPN detection, and an explainable risk score separate a real API from a thin one.

ByGeoIPHub TeamPublishedUpdatedReading time14 min read
Glass cubes with one fully lit and others partly lit, representing comparing IP data services

Choosing a provider for IP intelligence data is deceptively hard, because every option presents itself identically. There is a long table of fields, a free tier, a world map, a page of logos. On paper they are interchangeable. Then you build against one, ship it, and discover that the connection type you were counting on is empty for half your traffic, the VPN flag missed the obvious datacenter address, and the "risk score" is a number with no explanation you can put in front of a customer.

The feature table cannot tell you any of that. What follows is the buyer's checklist that can: the six things that actually separate a real IP data service from a thin one, what to ask about each, and, so you have a concrete reference point, how we answer each at GeoIPHub. Use it to interrogate any provider on the list, us included.

Two lenses projecting different response shapes from the same node, representing the same IP looked up in different services
Same IPs, different answers: that is the only fair test.

Why They All Look the Same on the Pricing Page

Two services can advertise the same field (say, connection_type) and deliver completely different things. One populates it for nearly every address from the global routing table. The other returns it only for a fraction of IPs, leaves the rest blank, and still lists it as a "feature." Both marketing pages say the same word.

This is the trap. IP data quality is invisible until you look at real responses, so the pricing page rewards whoever claims the most, not whoever returns the most. The entire skill of choosing well is refusing to evaluate on claims. Every axis below is written to be checked against an actual JSON response, not a checkbox.

1. Data Completeness, and Where It's Gated

Start with the headline number, then immediately distrust it.

A modern IP intelligence response is legitimately large: around 100 fields across 10 response groups: the network (ASN, ISP, connection type), approximate geolocation, WHOIS/registry data, reverse DNS, VPN/proxy/Tor/hosting detection, threat and bot signals, and a risk score. We break every one of those down in the complete list of IP data fields. That is a reasonable ceiling. Be wary of headline counts far above it. A field only counts if it is actually populated for the address you looked up, and padded schemas full of empty or placeholder fields inflate the number without adding a single decision.

The more important question is not how many fields, but which fields, on which plan. Here is the pattern to watch for: most providers advertise the full schema, then gate the valuable half (ISP, connection type, VPN/proxy detection, the provider name, and any risk score) behind paid tiers, leaving the free and entry plans as little more than country plus ASN. Country plus ASN cannot carry a fraud or access decision, so the "free tier" is really a demo.

How GeoIPHub answers it: every field is returned on every plan, including the free tier: 1,500 lookups per day with no field paywall. The connection type, the VPN provider name, the threat signals and the risk score are all present on the free plan, which is enough to build and validate a real integration before you spend anything. That is a deliberate position, and it is the one we would tell a buyer to demand from anyone.

2. Verified Detection, Not a Static List

This is the axis that separates the services that do the work from the ones that resell a dataset.

VPN and proxy detection can be built two ways. The common way is a static list: an address block is labelled a VPN because it appeared on a feed, and it stays labelled until the next refresh, by which point the infrastructure has often rotated. A great many IP APIs are, under the hood, a re-serving of lists like this, which is why their flags drift out of date and why they can rarely tell you why an address was flagged.

The better way is verification: actively probing the address for the ports and protocols that VPN and proxy software actually run, and cross-referencing the operators' own published server lists so the flag reflects what the address is doing now. The practical test for a buyer is simple: ask a candidate to name the VPN provider behind a flagged IP and explain the signal. A list-based service usually cannot; a verifying one can.

How GeoIPHub answers it: VPN and proxy flags are backed by active probing across 25+ ports and 8 protocols with real handshake probes, combined with VPN server lists pulled from 12 providers' own APIs plus a public third-party list (NordVPN, Mullvad and others), so a flagged address carries the signals behind it in scoring.detection_methods rather than a bare boolean. The vpn_provider field is meant to name the provider, but in our own lookups it still returns "none" for some listed servers, so don't count on provider naming yet. We walk through the mechanism in how VPN and proxy detection works, and you can run it against your own connection with the IP lookup tool. One honest caveat, because it belongs in a buyer's guide: detection recall is never perfect for anyone, so we describe the method, not a magic accuracy percentage, a point we make plainly in how accurate IP geolocation really is.

A real VPN lookup shows the evidence, not just the flag

A verified VPN flag comes with the reasons attached, and you can see that in one real response. We looked up 102.129.235.17, a commercial VPN server in Washington D.C., on 2026-10-05 (results change as ranges move). Trimmed to the groups that matter here:

JSON
{ "ip": "102.129.235.17", "asn": { "asn": 834, "org": "IPXO - IPXO LLC", "asn_type": "vpn", "connection_type": "datacenter" }, "detection": { "is_vpn": true, "is_anonymous": true, "vpn_provider": "none", "vpn_confidence": 100 }, "scoring": { "fraud_score": 92, "confidence": 0.76, "recommended_action": "block", "detection_methods": ["known_vpn_server", "openvpn_open", "ipsec_open"] } }

The detection_methods array is the audit trail. On that date known_vpn_server meant the address was flagged as a VPN, and openvpn_open and ipsec_open meant it answered real OpenVPN and IPsec handshakes when we probed it. A fraud_score of 92 was above the 75 line, so recommended_action was block. Our scoring has changed since 10 November 2026: an unnamed VPN found only by our handshake now gets vpn_service_unattributed, openvpn_open and ipsec_open can also come from a provider's list of the protocols a server offers, and a VPN with no abuse, proxy or Tor evidence stops at 70, step_up. Note what it doesn't show: vpn_provider is "none", so this response proves the flag but doesn't name the operator. That gap is ours to fix, and it's exactly the kind of thing you only find by reading raw JSON.

3. Connection Type and ASN Quality

If you only get one field right, make it this one.

The distinction between a residential address (a home broadband line, where your real customers are) and a datacenter address (a rented server, where the bots, scripts and scrapers live) is the single highest-signal data point in all of IP intelligence. It comes from the global routing table rather than a guess about physical location, which makes it among the most reliable fields you can ask for, if the provider maintains the hosting and cloud coverage to populate it accurately.

The test is coverage. A thin service knows the big three clouds and little else, so a checkout from a second-tier hosting provider sails through labelled "residential." A serious one tracks the long tail of hosting networks.

How GeoIPHub answers it: connection-type and hosting classification are backed by 853 hosting ASNs plus 10 cloud range feeds, so datacenter origin is caught well beyond the obvious names. The reasoning behind why this field matters so much is in what a datacenter IP address is.

4. An Explainable Risk Score

Plenty of services will hand you a single risk number. Far fewer will tell you what went into it, and an unexplained score is a liability, not an asset.

The moment you act on a score (challenge a login, hold an order, decline a signup), someone can ask you why, and "the vendor's number said so" is not an answer you want to give a customer or a compliance reviewer. A good risk score is explainable: it exposes the individual signals that fired, weights them, subtracts exonerating signals so shared and mobile addresses are not punished, and maps to clear thresholds you control.

Ask any candidate: does the score come with an audit trail, and can it tell the difference between "add points" and "subtract points"? A black box cannot.

How GeoIPHub answers it: the score combines 40 weighted reasons, including exonerating ones, into a 0-100 value with a recommended action across four bands (allow ≤25, review ≤50, step_up ≤75, block >75) and a detection_methods array naming exactly which signals fired. You can defend every decision it produces. We list every reason the score can name, with its weight, and you can see a live score for any address with the IP fraud score check.

5. Freshness: How Current the Data Actually Is

IP intelligence is perishable. Address space is reassigned, hosting ranges are added, Tor relays and VPN servers come and go daily. A dataset that is refreshed on a slow cadence is quietly wrong for a growing slice of traffic between updates, and you will never see it happen.

Ask how often each kind of data updates, and what happens when the service meets an address it has never classified. The weak answer is "we refresh the database periodically." The strong answer distinguishes between data that updates daily and addresses that are classified live, on demand.

How GeoIPHub answers it: the Tor exit list is refreshed daily, WHOIS is drawn live from the 5 RIR RDAP registries, static geolocation resolves through sub-millisecond MMDB lookups, and an address the system has not seen is classified live in under 2.5 seconds rather than returning stale or empty data. The signal base is drawn from 30+ data sources and 19 official crawler and AI-bot range feeds so bot and crawler verification stays current too.

6. An Honest Free Tier and a Simple Integration

The last axis is the one that predicts your whole experience with a vendor, because it reveals their intent.

An honest free tier is one you can genuinely evaluate and even run small production workloads on (the complete data, a workable daily limit), not a crippled demo engineered to force an upgrade before you have learned anything. And integration should be one request against one endpoint returning one predictable JSON object, not a multi-step dance. If it takes an afternoon to get a first useful response, that cost recurs for everyone who ever builds against it.

How GeoIPHub answers it: the free tier is 1,500 lookups per day with every field, anonymous access is available at 30 lookups per minute for quick tests, and the whole service is a single GET https://api.geoiphub.com/v1/lookup/{ip} returning one JSON document. You can start reading real responses in a minute, which is exactly the point: a buyer should never have to take completeness on faith.

GeoIPHub vs the Typical IP Data Service

Pulling the six axes together, here is the shape of the difference. The first block describes the pattern you will commonly meet when you read real responses across the market; the second block is what GeoIPHub returns, all of it verifiable on the free tier.

The typical IP data service

  • Field access: Full schema advertised; ISP, connection type, VPN flags and score gated behind paid tiers
  • VPN / proxy detection: Commonly a static list or resold feed; bare true/false, goes stale between refreshes
  • Connection type / hosting: Knows the major clouds; misses the long tail of hosting providers
  • Risk score: A single opaque number with no breakdown
  • Freshness: "Database refreshed periodically"
  • Free tier: Country + ASN demo, enough to force an upgrade

GeoIPHub

  • Field access: 110 fields across 10 groups, all returned on every plan including free
  • VPN / proxy detection: Active probing (25+ ports, 8 protocols) + 12 providers' own server lists plus a public third-party list, with the signals that fired listed in detection_methods
  • Connection type / hosting: 853 hosting ASNs + 10 cloud range feeds behind the residential-vs-datacenter call
  • Risk score: 0-100 with 40 weighted reasons, exonerating ones included, four action bands, and a detection_methods audit trail
  • Freshness: Tor list daily, live RDAP WHOIS, unknown IPs classified live in under 2.5s
  • Free tier: 1,500 lookups/day with all fields; anonymous 30/min for quick tests

The first block is written in the general, deliberately, because the honest thing to say is that these are patterns you will commonly encounter, not a claim about any one named provider. The point of this comparison is not to score anyone else. It is to give you the questions, so you can fill in that first block yourself for whatever shortlist you are holding.

What a Trustworthy Provider Won't Claim

A buyer's guide that only lists strengths is a sales page. So here is the other side, because how a provider talks about its limits is itself a quality signal.

No IP data service can place an address at a street or name a person. Geolocation is an approximate, city-to-region estimate at best, and it is weaker still on mobile, CGNAT and VPN connections. GeoIPHub returns a geo_confidence value that can be low or zero for anycast and infrastructure IPs precisely because those addresses have no single physical home, and we would rather return honest uncertainty than a confident guess. We also don't inflate the field count, promise a perfect detection rate, or claim address-level precision. A provider that promises pinpoint accuracy from an IP alone is telling you something useful (that it is willing to oversell), and that is worth knowing before you build.

Evaluate Any Service in Ten Minutes

  • Read raw JSON, not the feature table. Run three or four addresses through each candidate and look at the actual response. Claims are free; populated fields are not.
  • Test a datacenter and a VPN IP. Use an address you know is hosted or on a VPN and confirm the connection type and VPN flag are correct and specific. A flag that lists the signals behind it beats a bare true.
  • Test a mobile IP. Check it is identified as mobile/CGNAT and treated leniently, not mislabelled and penalised. This is where false positives are born.
  • Demand an explanation from the score. If the risk number can't tell you which signals fired, you can't defend the decisions you make with it.
  • Check the plan you'd actually buy. Confirm the fields you need are populated on that tier, not merely documented on the pricing page.
  • Time the first useful response. One endpoint, one JSON object, a minute to first result. Friction here recurs forever.

The best IP data service is not the one that wins the feature-table comparison. It is the one whose real responses survive ten minutes of skeptical reading: complete on the plan you can afford, verified rather than guessed, and honest about what it cannot know. Hold every provider to that standard, GeoIPHub included, and the choice makes itself.

Frequently Asked Questions

What makes the best IP data service?

Three things that never appear on a pricing page. First, complete data on every plan: the useful fields (ISP, connection type, VPN/proxy flags, the risk score) available without a paywall, not just country and ASN on the free tier. Second, detection that is verified rather than guessed, meaning VPN and proxy flags built from active network probing and providers' own server lists, not a stale static list. Third, an explainable risk score that returns the exact signals that fired, so a decision can be defended instead of trusted blindly. Field count and a map are table stakes; those three are what separate a real IP intelligence API from a thin one.

How many data fields should an IP intelligence API return?

Enough to make a decision, corroborated across independent groups. Roughly 100 fields organised into 10 response groups is a realistic modern figure: the network (ASN, ISP, connection type), approximate geolocation, WHOIS/registry data, reverse DNS, VPN/proxy/Tor/hosting detection, threat and bot signals, and a risk score. Be skeptical of headline counts far above that; a field only matters if it is actually populated for the IP you looked up, and many advertised fields come back empty or as placeholders. Ask for a real sample response before you count.

Is a free IP data API good enough for production?

It depends entirely on whether the free tier is honest or a demo. Many providers gate the valuable fields (ISP, connection type, VPN/proxy detection, the risk score) behind paid plans, leaving the free tier as little more than country plus ASN, which is not enough to make a fraud or access decision. A genuinely useful free tier returns every field. GeoIPHub, for example, returns all fields on the free tier with 1,500 lookups per day and no field paywall, which is enough to build and validate a real integration before spending anything.

How do I evaluate an IP data provider before committing?

Run the same handful of addresses through each candidate and read the raw JSON, not the marketing. Use an IP you know is a datacenter or VPN and check whether the connection type and VPN flag are correct and specific; use a mobile IP and check whether it is correctly identified rather than mislabelled; and check whether the risk score explains which signals it used. Then confirm the fields you need are populated on the plan you would actually buy, not just documented. Ten minutes of reading real responses tells you more than any feature table.

Why does 'verified' VPN detection matter more than a big blocklist?

Because a list goes stale the moment it is published, and IP infrastructure rotates constantly. Verified detection reflects what the address is doing now, because it actively probes the address for the ports and protocols VPN and proxy software actually run and cross-references providers' own published server lists, instead of trusting whatever a list said when it was last compiled. The practical test is whether the service can tell you why an address was flagged, naming the signals that fired, rather than just returning a bare true/false from a dataset you cannot inspect.

Written by

GeoIPHub Team

The team behind the GeoIPHub API

Written by the GeoIPHub team, the people who build the GeoIPHub IP intelligence API and its scanner. Drafts are prepared with AI assistance and edited by the team; API examples are real lookups against the live API unless labelled illustrative.

Share this article
More articles

Related posts