Product review
Castle residential proxy detection review
Castle now offers standalone IP Intelligence alongside its broader risk platform. The residential_proxy_access signal records recent observed residential-proxy participation, while connection type and tunnel data answer separate network questions.
Editorial score
- Evidence layer
- Standalone IP intelligence and device-aware risk
- Free access
- 5 US dollars monthly shared API credit
- Paid entry
- Pro: 200 US dollars monthly shared API credit
Key facts
- Residential signal
- residential_proxy_access marks IPs observed in a residential-proxy provider network within the last seven days. Vendor page ↗
- Network context
- Connection type covers residential, datacenter, corporate and mobile. Tunnel data can include type, operator, last-seen time and proxy subtype. Vendor page ↗
- Important distinction
- The generic ip.privacy.proxy flag can remain false when residential_proxy_access is true. Interpret each documented field according to its own meaning. Vendor page ↗
- Pricing
- Free includes 5 US dollars monthly shared API credit, equivalent to 5,000 IP lookups or 1,000 Risk/Filter calls. Pro includes 200 US dollars credit. Mixed usage consumes the same credit pool. Vendor page ↗
Strengths
- A standalone IP endpoint separates network enrichment from full Risk integration.
- Dedicated recent residential-proxy activity is distinct from ISP connection type.
- A small monthly shared credit supports an initial API evaluation.
Limitations
- Recent observation has a defined seven-day scope; no match is not proof of a legitimate visit.
- Generic privacy.proxy and residential_proxy_access are not interchangeable fields.
- IP lookups and Risk/Filter calls consume the same monetary credit at different rates.
Who it fits
Teams needing an IP intelligence API or combining network evidence with Castle’s device-aware risk and policy workflow.
Use the alternatives by evidence layer to compare IP feeds, live session checks and managed traffic protection.
What the score means
The 8.0 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
Test observed and unobserved permitted exits, inspect connection/tunnel fields and residential_proxy_access separately, then compare standalone IP calls with a complete Risk integration where needed.
Free shared API credit
Select the free plan to evaluate the required endpoint. Treat 5,000 IP lookups and 1,000 Risk/Filter calls as alternatives, not two cumulative quotas.
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
Why can proxy be false while residential_proxy_access is true?
The documentation defines the signals separately. The dedicated field records observed residential-proxy access; the generic privacy field is not its replacement.
What does free credit cover?
The 5 US dollars monthly credit is shared across APIs. It is equivalent to 5,000 IP lookups or 1,000 Risk/Filter calls at the listed rates.
Does an IP lookup include device identity?
The standalone IP endpoint supplies network intelligence. Device-aware Risk evaluation is a separate integration route.
Explore checkers, demos and evaluation routes →