What Is a Residential Proxy? How It Works and When to Use One
How residential proxies route traffic through real home IPs, where those IPs come from, what they are good for, where they fall short, and how to choose a provider.
By the Proxonym team
A residential proxy is an intermediary server that forwards your requests through an IP address that an internet service provider assigned to a real home connection. The website you visit sees an ordinary household visitor in a specific country, city or network instead of your server. Providers build these networks from devices whose owners opted in to share bandwidth, and expose them through a gateway that picks an IP for each request.
That is the whole idea. The details, covered below, decide whether a residential proxy is the right tool for a job: how traffic flows, where the IPs come from, what they are good at, and where they fall short.
How a residential proxy works#
Three parts work together: a network of peers, a gateway, and a rotation policy.
The peer network#
Peers are consumer devices running partner apps or SDKs whose users agreed to share their bandwidth. Each peer's IP belongs to its ISP, so traffic leaving it carries the reputation of a normal broadband subscriber. The pool changes constantly as devices come online and go offline, which is why providers quote pool sizes rather than fixed lists. Our residential network counts 55M+ IPs in 195+ countries, with the largest pools in the United States (8.3M), Brazil (5.2M), India (3.2M) and the United Kingdom (2.3M).
The gateway#
You never connect to peers directly. You connect to one endpoint, gw.proxonym.com on port 8000 for HTTP and HTTPS or port 1080 for SOCKS5, and authenticate with a username and password. The gateway then:
- checks your credentials and traffic balance;
- reads targeting parameters from your username, such as country, city or ASN;
- selects an available peer that matches;
- relays your request to the target through that peer and streams the response back.
For HTTPS sites, your client opens a CONNECT tunnel and negotiates TLS directly with the target, so the peer relays encrypted bytes it cannot read. Targeting is part of the username:
# Exit through a residential IP in New York City
curl -x http://gw.proxonym.com:8000 \
-U "USERNAME-country-us-city-new_york:PASSWORD" \
https://api.ipify.orgRotation and sticky sessions#
By default the gateway assigns a new IP to every request. That spreads load across the pool and keeps the request rate of each IP low. When a flow needs continuity, such as a login or a multi-page checkout, add a session ID to the username (-session-a7k2) and the same IP is kept for up to 120 minutes. Rotating vs sticky sessions explains how to pick a lifetime.
Ethical sourcing: where the IPs come from#
A residential proxy network is only as legitimate as the consent behind it. The same technology can be built ethically or from compromised devices, and buyers rarely see the difference until something goes wrong.
An ethical network has three properties:
- Opt-in: people join through partner apps or SDKs and actively agree to share bandwidth.
- Informed: they are told in plain language what sharing means, not in buried fine print.
- Reversible: they can opt out at any time.
That is how our network is built. On the demand side, abusive targets are blocked at the network level and sensitive use cases require verification. The ethics and IP sourcing page describes the model in detail.
Sourcing also matters for practical reasons. IPs harvested from malware-infected devices land on blocklists quickly, vanish when the infection is cleaned up, and expose any business that uses them to legal and reputational risk.
What residential proxies are used for#
- Web scraping: collecting public data from sites that block hosting IPs.
- Price and stock monitoring: seeing the prices and availability that shoppers in each market see.
- SEO and SERP tracking: checking rankings from a specific city, since results vary by location.
- Ad verification: confirming that ads render correctly and reach the intended region.
- Market research: gathering localized content, reviews and listings.
- Brand protection: finding counterfeits and phishing pages that hide behind geo-blocks.
- AI training data: feeding datasets and retrieval pipelines with fresh public web data.
What these have in common: the target treats visitors differently based on where they appear to come from, and hosting IPs either get blocked or see a different version of the site.
Related proxy types#
Two close relatives are worth knowing. Mobile proxies route through 3G, 4G and 5G carrier IPs, which platforms built for phones trust most; ours cover the United States, the United Kingdom and Austria, rotate per connection and share the residential GB balance. ISP proxies are static IPs registered to consumer ISPs but hosted in data centers, so they keep one address for days or months at datacenter speed.
Limitations to plan for#
- Latency varies. Each request travels through a consumer connection, so response times are higher and less predictable than on datacenter IPs. Set generous timeouts and retry on failure.
- Billing is per GB. Heavy pages, images and video add up. Block media you do not need, and for terabyte-scale jobs compare unlimited residential plans, which bill by bandwidth.
- Sessions can end early. A peer may go offline before your sticky lifetime ends. Design multi-step flows to recover, for example by logging in again.
- No long-term identity. Sticky sessions last up to 120 minutes. For an IP that stays yours for days or months, use static ISP proxies.
- An IP is not a fingerprint. A residential IP does not fix inconsistent headers, a bot-like request pattern or aggressive request rates. Sites look at all of it.
- The rules still apply. Proxies do not change the law or a site's terms, and our acceptable use policy applies to every request.
If you are weighing residential against cheaper options, residential vs datacenter proxies walks through the trade-off with real numbers.
How to choose a residential proxy provider#
Use this checklist when you compare providers, us included:
- Sourcing: is the consent model documented, and can peers opt out?
- Coverage where you need it: ask for IP counts in your target countries, not only a global total.
- Targeting depth: country, state, city and ASN. City and ASN targeting matter for local SEO and ISP-specific testing.
- Session control: rotation per request, and the maximum sticky lifetime.
- Protocols: HTTP, HTTPS and SOCKS5, with ports and setup clearly documented.
- Pricing terms: the price per GB at your volume, how long traffic stays valid, and whether plans auto-renew. Our packs start at 5 GB for $9.95, come with 30, 60 or 90-day or no-expiry validity, and never auto-renew.
- A real test: buy a small pack and measure the success rate on your own targets. Benchmarks run on other sites tell you little about yours.
- Visibility: usage reporting, sub-users with their own traffic limits, and an API to automate both.
- Support: a human who answers at the hour your jobs run. Ours is available 24/7 by email.
- Enforcement: an acceptable use policy that is actually enforced keeps the pool clean for every customer.
Our tiers are listed on the pricing page, and the documentation covers every username parameter.
Key takeaways#
- A residential proxy routes your requests through real home IPs via a gateway, so targets see a household visitor.
- Rotation per request spreads load; sticky sessions hold one IP for multi-step flows.
- Consent is the line between an ethical network and a botnet, so ask every provider how its IPs are sourced.
- Expect higher latency and per-GB costs, and use static ISP IPs when you need a long-lived identity.
- Choose a provider by testing on your own targets, not by headline pool size.
