Screen sign-ups against sanctioned jurisdictions
Example
See more Fintech use cases → New account → 5.62.x.x
country: sanctioned jurisdiction → block onboarding, log for audit
Use case
IP Geolocation API for Regulatory & Jurisdiction Compliance
Know which rules apply before you act — jurisdiction, sanctions, tax, residency, and age-gating from one lookup.
Nearly every regulated action depends on one question: where is this request coming from? One IP lookup gives you the country, EU status, and region to screen sanctions, apply the right tax, honour licensing territories, and enforce residency — before you commit to anything.
Who uses it
The teams that lean on this most, in rough order of how often we see it.
The signals it uses
Every one ships in the standard response — no add-ons, no tiers.
country / countryCode Jurisdiction and sanctions screening is_in_eu GDPR, VAT, and EU consumer-protection rules region State / province tax, licensing, and residency security (isVpn / isTor) Flag attempts to evade a jurisdiction check connection (ASN / org) Corroborate the visitor's stated location How different teams put it to work
The same lookup, applied to the rules each industry has to meet.
Apply the right VAT/GST and consumer rules
Example
See more E-commerce use cases → Checkout → 92.184.x.x
country: France · is_in_eu: true → 20% VAT + EU consent + returns policy
Enforce licence territory and age-gating
Example
See more iGaming use cases → Bet placement → 81.2.x.x
country: UK → licensed territory, trigger UK age/KYC flow
Honour state telehealth licensing
Example
See more Healthcare use cases → Consult request → 73.9.x.x
region: Texas → match to a TX-licensed provider only
Enforce data-residency and domestic access
Example
See more Government use cases → Portal access → 203.0.x.x
country: outside jurisdiction → deny, route to domestic channel
Respect content licensing jurisdictions
Example
See more Media use cases → Content request → 193.1.x.x
country: Ireland → serve EU-licensed catalogue only
Common questions
Is IP geolocation enough for regulatory compliance?
It's a strong first signal, not the whole control. It establishes the likely jurisdiction for tax, sanctions, licensing, and residency decisions in real time. For regulated flows, pair it with the identity, KYC, and documentation checks your framework requires — IP tells you which rules probably apply; your compliance stack confirms and records them.
How do you handle users who hide behind a VPN?
The response flags common VPN, proxy, and Tor exits and datacentre networks, so a jurisdiction check can challenge or escalate when the signals suggest evasion. Treat these as risk signals that trigger step-up verification, not as automatic proof of wrongdoing.
Does it help with EU-specific rules like GDPR and VAT?
Yes. The response includes an is_in_eu flag alongside the country, so you can apply EU VAT, consent banners, and consumer-protection rules precisely, and treat EU and non-EU traffic differently from the first request.
Check jurisdiction in one request
Free tier: 2,000 lookups/day, no card. Paid plans from $2.50/month. One call per request, under 50ms median response.