Product review
ipregistry proxy detection API review
Ipregistry gives developers structured IP intelligence in a single response: location, network ownership, carrier and security fields. Its security object separates proxy, VPN, Tor and relay indicators. That makes it useful when an application needs predictable network enrichment and an explicitly maintained decision policy.
Editorial score
- Evidence layer
- IP geolocation with structured security fields
- Free access
- 20,000 free credits at signup; full response fields
- Paid entry
- 29 US dollars per month for 100,000 credits; annual option available
Key facts
- Response
- Structured security fields include proxy, VPN, Tor and relay indicators, alongside IP/network/location enrichment. Vendor page ↗
- Plan access
- All plans include the full response. Pricing lists 20,000 free signup credits and Starter at 29 US dollars per month for 100,000 credits. Vendor page ↗
- Usage
- One IP lookup uses one credit. Bulk and filtering features are documented separately. Vendor page ↗
- Integration
- API authentication, libraries, bulk lookups and error codes are described in the documentation. Vendor page ↗
Strengths
- Consistent structured network and security response.
- Full response access is not held back for higher subscription tiers.
Limitations
- Structured IP flags do not establish that a particular account is abusive.
- Track whether missing data means unavailable, unknown or a negative result before normalizing responses.
Who it fits
Engineering teams that want geolocation and security fields in one predictable IP response.
Use the alternatives by integration model to compare IP lookup APIs, browser-assisted collection, attribution feeds and local databases.
What the score means
The 8.6 out of 10 score is an editorial assessment under the same 42-criterion, seven-category framework. The rubric covers detection, integration, latency, response shape, freshness, false-positive discipline and commercial access. The published scale runs from 0 to 10.
The award and score are distinct. Read all criteria and relative weights and verify the required signal and integration for your traffic.
How to evaluate it
Compare known proxy and legitimate shared-network IPs. Log which security fields are populated, the observation window, unknown cases and the action your application would take.
Developer access and documentation
Create developer access and inspect permitted IPs through the documented security fields.
Open evaluation routeSources and further reading
- Product and detection approach · checked October 23, 2026
- Pricing and access · checked October 23, 2026
- Integration and result documentation · checked October 23, 2026
- Vendor guide and product context · checked October 23, 2026
FAQ
Does the free credit balance include security fields?
The pricing page says every plan provides the full response. Confirm the account allowance before a production rollout.
Is there a graded fraud score?
The security fields are structured classifications. Keep them separate from a provider-specific fraud score when normalizing your internal model.
What does one credit buy?
The pricing page defines one lookup as one request and one credit.