Product review
IPQualityScore residential proxy detection review
IPQualityScore combines IP risk and anonymity checks with abuse intelligence. Its residential-proxy feed is a separate filtered threat-data route; evaluate that product separately from a live API lookup and its risk settings.
Editorial score
- Evidence layer
- IP risk API and residential threat feed
- Free access
- 1,000 free lookups advertised; confirm API scope
- Paid entry
- Confirm the current API plan and included lookups
Key facts
- API output
- The API documents proxy, VPN, Tor and fraud_score fields, plus recent abuse, connection type and other contextual results. Field availability depends on the request and service. Vendor page ↗
- False-positive controls
- Documentation recommends strictness zero or one for fewer false positives; higher strictness can increase latency and false positives. Public-access-point settings cover relevant shared-network cases. Vendor page ↗
- Residential feed
- The residential-proxy detection feed filters the wider abuse feed for residential threats and supports daily CSV delivery. It is not simply the live lookup response. Vendor page ↗
- Evaluation
- A public IP lookup is available. Confirm current automated API limits and commercial terms for the required output and volume. Vendor page ↗
- Free access
- The public checker advertises 1,000 free lookups. Confirm the current API conditions and required residential output; no monthly reset is assumed. Vendor page ↗
Strengths
- Inspectable IP risk and recent-abuse context fit an existing fraud workflow.
- Strictness and shared-network settings provide explicit tuning choices.
- API and feed routes cover different operational requirements.
Limitations
- A residential connection_type describes the network, not proof of proxy use.
- Strictness changes affect the trade-off between detected cases, latency and legitimate-user restrictions.
- Manual checker access does not establish automated API quotas or residential-feed licensing.
Who it fits
Fraud teams adding IP risk, anonymity and recent-abuse context to a server-side transaction or registration pipeline.
Use the alternatives by evidence layer to compare IP feeds, live session checks and managed traffic protection.
What the score means
The 8.7 out of 10 score is an editorial assessment under the same 36-criterion, six-category framework. The rubric emphasizes residential-proxy coverage, false-positive control and corroboration beyond IP ownership. A score is not a measured detection percentage.
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
Run controlled proxy and known legitimate shared-network cases at the same strictness. Inspect proxy indicators separately from fraud score, and compare latency and review outcomes before raising strictness.
Public IP lookup and API documentation
Test permitted IP addresses in the public checker, then confirm an API plan and the exact settings used in your integration.
Open evaluation routeSources and further reading
- Product and detection approach · checked October 21, 2026
- Pricing and access · checked October 21, 2026
- Integration and result documentation · checked October 21, 2026
- Vendor guide and product context · checked October 21, 2026
FAQ
Is a high fraud score the same as a residential-proxy label?
No. A fraud score combines risk evidence; inspect the actual proxy fields and the context returned for the relevant product.
How should strictness be chosen?
Start from the documented lower-strictness guidance and measure controlled detections and legitimate-user restrictions together before changing it.
Can I test an IP without integrating?
The public IP lookup is an evaluation route. Automated API allowances and feed access need confirmation through the current plan.
Explore checkers, demos and evaluation routes →