Where is this request really from?
Location, network owner, and whether the address is a Tor exit, a cloud server or a hosting provider, the places fake signups and card testing come from.
1 credit per check 路 from $2.00 per 1,000 credits 路 credits never expire
curl https://api.verified.net/v1/ip \
-H "Authorization: Bearer $VERIFIED_KEY" \
-d '{"ip": "8.8.8.8"}'What you get.
Geolocation
Continent, country, region, city and coordinates (city-level, approximate).
Network
ASN and organization.
Tor exits
Current Tor exit nodes, refreshed daily.
Datacenter and hosting
Cloud provider ranges plus hosting networks by ASN.
Risk score and verdict
Tor rejects, datacenters go to review, everything else accepts.
Fast
All data is on our own servers, so answers come back in milliseconds.
One request.
POST /v1/ip with your API key. JSON back in milliseconds, with the facts and an accept, review or reject verdict.
API documentationcurl https://api.verified.net/v1/ip \
-H "Authorization: Bearer $VERIFIED_KEY" \
-d '{"ip": "8.8.8.8"}'Questions.
Do you detect VPNs?
Not as a separate flag. Many commercial VPNs run on datacenter networks, which we do flag.
Are private addresses charged?
No. Private, loopback and other non-public addresses are answered free.
Where does the location data come from?
DB-IP's database, updated monthly, plus public Tor and cloud provider lists.