Updated 2026-09-29
Know what is behind the address before you trust the session: VPN, proxy, Tor, residential proxy, datacenter or a compromised machine - with the network owner, the location and a risk score that explains itself.
curl -X POST "https://api.digifootprint.dev/v2/ip" \
-H "Authorization: Bearer dfp_your_key" \
-H "Content-Type: application/json" \
-d '{"ip": "185.220.101.1"}'{
"lookupId": "c242b368-...",
"ip": {
"address": "185.220.101.1",
"isProxy": true,
"isVpn": false,
"isTor": true,
"isHosting": false,
"isResidentialProxy": null,
"isCompromised": true,
"isAnonymous": true,
"operator": "TOR",
"asn": "AS60729",
"connectionType": "Business",
"location": { "countryCode": "DE", "city": "Brandenburg an der Havel", "timezone": "Europe/Berlin" },
"risk": { "score": 90 }
}
}Anonymity flags - VPN, proxy, Tor, residential proxy, datacenter hosting, known automated traffic and compromised machines - each on its own, because a datacenter address and a botnet victim mean different things. Network - operator (the VPN brand when known), ASN, ISP and connection type. Location - country, region, city, coordinates and timezone.
A risk score you can read. The score is the total of the named signals that fired, and every rule can be tuned for your own traffic from the dashboard. Unknown is never clean: when only location could be answered, the risk flags are null, not false.