See through VPNs, proxies and Tor
Resolve every IP at the network layer — VPN, proxy, Tor, datacenter and residential-proxy exits, with ASN, reputation and geo — from live, self-hosted datasets.
Why IP lists alone are not enough
Blocking datacenter ranges catches the lazy fraudster. The serious ones buy residential-proxy access — real consumer IPs that sail past any IP blocklist. Robust network intelligence has to combine curated IP data with reputation and behavior, and it has to stay fresh. Prynt ships all of it, and because it is self-hosted, the raw IP data never leaves your infrastructure.
VPN & proxy pools
Match against continuously refreshed VPN and open/anonymous-proxy IP pools — updated on a cron so coverage never goes stale.
Datacenter CIDRs
Thousands of datacenter and hosting-provider ranges flag traffic that claims to be a home user but originates in the cloud.
Tor exit nodes
The live Tor exit-node list is ingested and matched so anonymized traffic is scored the moment it arrives.
Residential proxies
The hardest class — caught with reputation-network signals, ASN anomalies and behavior, not naive IP lists alone.
IP reputation
A blocklist of known-abusive IPs feeds a reputation score you can weigh in your own rules.
ASN & geo
Autonomous-system and geolocation context surface hosting ASNs and location mismatches behind an anonymizer.
Live datasets, refreshed automatically
Prynt bind-mounts IP datasets and refreshes them on a schedule — datacenter CIDRs, Tor exits, VPN pools and an abuse blocklist — so detection improves without a redeploy. Optional MaxMind GeoLite2 adds ASN and city-level geo.
Score it, then act
Every check contributes to the suspect score with explicit reason codes
(VPN_DETECTED, DATACENTER_IP, TOR_EXIT), so you decide
whether an anonymized session is allowed, challenged with Prynt
Challenge, or blocked — per action, per tenant.
Related
Bot detection · Account takeover · Device fingerprinting · Residential proxy detection · VPN detection guide · Glossary