Relay
Signal Review

Product review

IPinfo proxy detection review

IPinfo’s residential-proxy data identifies observed proxy exits rather than merely labeling an address as belonging to a residential ISP. Provider and recency fields make the result useful for an existing IP-enrichment pipeline.

8.6 / 10

Editorial score

Evidence layer
Observed-exit IP intelligence
Free access
IPinfo Lite: country and ASN; separate from residential data
Paid entry
Core: 26 US dollars/month billed annually for basic anonymity flags; Max: 163 US dollars/month billed annually adds detailed residential data

Key facts

Data
Residential-proxy output includes provider attribution, last-seen information and frequency information where available. Vendor page ↗
Observation windows
The residential-proxy API uses a seven-day window; the downloadable database uses 30 days. Interpret last_seen and percent_days_seen within the relevant product window. Vendor page ↗
Current access
Core provides limited anonymity and hosting flags with 150,000 monthly requests for 310 US dollars billed annually (displayed as 26 US dollars/month). Max adds detailed VPN/proxy/relay and residential data with 250,000 monthly requests for 1,960 US dollars billed annually (displayed as 163 US dollars/month). Vendor page ↗
Product separation
IPinfo Lite’s free country/ASN access is not the Max residential-proxy dataset. Downloadable database licensing is a separate commercial route. Vendor page ↗
Field entitlement
Core returns limited is_anonymous and is_hosting flags. Detailed VPN/proxy/relay fields and residential observations require the applicable higher tier or custom API; an inclusive pricing label is not the full response schema. Vendor page ↗

Strengths

  • Observed exit activity adds evidence beyond ISP ownership.
  • Provider, last-seen and frequency context support freshness-aware handling.
  • A server-side API fits an established enrichment pipeline without requiring a browser identity product.

Limitations

  • A previously unobserved exit may have no residential-proxy observation; no match is not proof that a visit is legitimate.
  • API and database windows differ, so raw percentages are not directly interchangeable.
  • An IP lookup does not by itself identify devices, users or coordinated account behavior.

Who it fits

Teams adding VPN, proxy and relay fields to IP enrichment, with Max or a data license when dedicated residential-proxy observations are needed.

Use the alternatives by evidence layer to compare IP feeds, live session checks and managed traffic protection.

What the score means

The 8.6 out of 10 score is an editorial assessment under the same 39-criterion, seven-category framework. The rubric emphasizes proxy coverage, false-positive control and corroboration beyond IP ownership. 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

Record known controlled exits, observation timestamps and the exact API or database version. Compare recently active, older and unmatched addresses, then join those results to session and account evidence.

Lite access and Max plan selection

Use Lite to inspect basic country/ASN integration. Select Max or arrange the appropriate residential dataset access to test proxy-provider and recency fields.

Open evaluation route

Sources and further reading

FAQ

Does a residential ASN prove proxy use?

No. ISP ownership and observed participation in a proxy network are different facts. IPinfo’s residential-proxy dataset adds the latter evidence.

Are API and database results based on the same period?

The documentation lists a seven-day API window and a 30-day database window. Compare recency and activity frequency within the relevant window.

Is the free Lite tier enough for residential-proxy data?

No. Lite provides basic country and ASN data; current residential-proxy access is listed in Max or the separately licensed data offering.

Summarize this page with