Screen bot sign-ups at registration
Example
See more SaaS use cases → New signup → 3.120.x.x · type: hosting
datacentre origin → challenge with verification before activating
Use case
IP Geolocation API for Signup & Account Security
Stop fake sign-ups and risky logins at the door — with network, anonymiser, and impossible-travel signals.
The cheapest fraud to stop is the account that never gets created. One IP lookup tells you whether a sign-up or login comes from a datacentre rather than a home ISP, whether it's behind a VPN or Tor, and whether a login implies impossible travel — so you can add friction exactly where it's needed.
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.
connection (ASN / org / type) Flag sign-ups and logins from datacentre networks security (isVpn / isTor) Spot anonymised registration and login attempts country / region / city Baseline a user's usual location latitude / longitude Impossible-travel checks between logins How different teams put it to work
The same signals, applied to the account abuse each team faces.
Flag suspicious account creation
Example
See more E-commerce use cases → Burst of signups → same hosting ASN
shared datacentre network → rate-limit and challenge
Block multi-account farming at the door
Example
See more Gaming use cases → New account → 45.83.x.x · isVpn: true
VPN + datacentre origin → require stronger verification
Protect logins with location baselines
Example
See more Fintech use cases → Login → country ≠ usual, 900km in 20 min
impossible travel → step-up MFA before granting access
Guard citizen-portal access
Example
See more Government use cases → Portal login → foreign hosting ASN
unexpected origin → additional identity check
Common questions
How does IP data stop fake account sign-ups?
Most bulk and bot registration comes from hosting and datacentre networks, not residential ISPs. Flagging that origin — plus VPN and Tor signals — at the sign-up step lets you challenge the suspicious minority with extra verification while letting genuine users through untouched.
What is impossible travel and how does it protect logins?
It compares the location of consecutive logins for one account. If two sessions are too far apart to be physically possible in the elapsed time, that's a strong account-takeover signal. Use it to trigger step-up MFA rather than to hard-block, since legitimate VPN use can also cause jumps.
Won't this block legitimate users on VPNs?
It shouldn't, if you use the flags as risk signals rather than automatic blocks. Many real users browse via VPN. The right pattern is to raise friction — an extra verification step — for higher-risk sign-ins, and let honest users clear it quickly.
Protect sign-ups in one request
Free tier: 2,000 lookups/day, no card. Paid plans from $2.50/month. One call per sign-in, under 50ms median response.