A residential proxy is a proxy server whose exit IP belongs to a home internet connection assigned by a consumer ISP, not to a hosting company. Your request goes to the provider's gateway, exits through a residential IP, and the target site sees a normal household visitor. The point is not encryption, it is classification: the IP resolves to an ISP that serves real customers, so it passes checks that reject hosting ranges.
How a residential proxy works
Three hops, always:
- Your client (browser, scraper, app) connects to the provider's gateway with a username, password, and usually targeting parameters for country, city, or session.
- The gateway forwards the request to an exit node: a device or line sitting on a residential ISP connection.
- The exit node makes the request to the target site and passes the response back. The site logs the residential IP, not yours.
The exit node is where providers differ. Some run their own ISP lines. Most large pools are peer-sourced: the IP belongs to a real person's router or phone, contributed through an SDK bundled into a free app or VPN. That sourcing decides both the ethics and the stability of the pool, which is covered in how free VPNs and proxies sell your device.
What makes an IP "residential"
Nothing in the packet says "residential". Platforms decide by lookup:
- ASN and IP-to-org data: the autonomous system number maps to a consumer ISP (Comcast, BT, Deutsche Telekom) rather than a cloud provider.
- Registry and rDNS records: reverse DNS on consumer lines usually looks like a dynamic pool hostname.
- Commercial IP-reputation feeds: vendors label ranges as hosting, VPN, proxy, residential, or mobile, and sell that label to sites. A "residential" IP that has been used by thousands of scrapers gets relabeled as proxy regardless of its ASN.
That last point matters more than most definitions admit. Residential is a property of the range, but trust is a property of the individual IP's recent history.
How is your current IP classified?
Types of residential proxies
Rotating residential
The gateway assigns a different exit IP per request or per short interval. Suits high-volume requests against public pages where each request stands alone: price checks, search results, catalog pages. Wrong for anything with a login, because a mid-flow IP change reads as session hijacking.
Static residential (ISP proxies)
One IP held for the life of the plan, hosted in a datacenter but announced under an ISP's ASN. Fast and stable, but the whole subnet is easy to identify, so heavily targeted platforms often treat static ISP ranges as commercial infrastructure.
Sticky sessions
A middle setting: the gateway pins you to one exit for a configured window, then releases it. Read what a sticky session is for how long to hold one.
Residential vs datacenter vs mobile
- Datacenter: IP owned by a hosting provider. Cheapest, fastest, easiest to identify and block in bulk. Fine for internal tooling and sites that do not care.
- Residential: consumer ISP IP, one household per address. Passes hosting filters, moderate speed, priced per GB.
- Mobile: IP assigned by a carrier to a phone behind CGNAT. Shared by many real subscribers at once, so a block hurts real customers and platforms rate-limit instead of banning. Highest trust, highest cost per GB.
The full breakdown of when each one is the right tool is in datacenter vs residential vs mobile proxies.
What residential proxies are used for
Legitimate work, mostly of four kinds:
- Market and price research: seeing a competitor's listings, shipping options, or search ranking as a local shopper sees them.
- Ad verification: confirming your creatives render in the geos you paid for and that no cloaked redirect is running.
- Localisation QA: checking that your own site, app, or CDN serves the right language, currency, and content per region.
- Account operations from a stable identity: managing accounts you legitimately own without every login arriving from an office datacenter range.
They are not appropriate for regaining access after a ban, faking engagement or clicks, or evading identity verification.
The failure mode most guides skip: peer churn
Peer-sourced residential pools depend on someone else's device staying online. When that person closes the app, walks out of Wi-Fi range, or their router reboots, your exit disappears. Symptoms look like site-side blocking but are not:
- A long scrape returns clean responses, then a burst of connection resets.
- A logged-in session drops to a re-authentication screen halfway through a multi-step flow.
- The same request works on retry from a different IP, so your logs show intermittent 403s with no pattern.
Decision rule: if a task has a login, a cart, or more than about a minute of state, do not put it on a rotating residential pool. Use a sticky window long enough to finish the task, verify the exit IP at the start of the flow with the IP Type Checker, and treat a mid-flow IP change as a fatal error your code handles, not something to retry blindly. If the task must never lose its IP, a dedicated device beats any shared pool.
Sourcing and the ethics problem
The cheaper a residential pool is, the more likely its IPs came from users who did not meaningfully consent, and the more likely they sit on abuse blacklists from whatever the previous tenant did. That combination produces the worst of both worlds: a "residential" label with datacenter-level trust. Why cheap residential proxies are often unethical IP traps covers what to ask a provider before buying.
What residential proxies cost
Pooled residential access is billed per gigabyte, and the per-GB rate falls as the commitment rises. Static and dedicated options are sold per month instead, because you are renting one line rather than access to a pool. Exact rates vary widely between providers, and the gap usually traces back to sourcing: the consent-and-blacklist problem above is what a suspiciously cheap pool is saving money on.
VoidMob does not sell residential proxies. We sell the tier above it in the trust hierarchy: mobile. The pay-per-GB pool runs from $3.99 for a single gigabyte down to $2.50 per GB at the largest tier, and dedicated 4G/5G devices start from $49 per month depending on country. Budget by workload, not by headline rate: a page-heavy scrape at 2 MB per page will spend gigabytes long before a login-and-post workflow does.
1What is a residential proxy used for?
Seeing the web as a local household user does: price and market research, ad verification, localisation QA of your own properties, SEO result checks, and logging into accounts you own from a consistent IP instead of an office or cloud range.
2Why would someone need a proxy?
Because the target site treats your real IP as a signal. A business checking competitor prices from its office range gets served different or blocked content; a team managing regional accounts from one building looks like one suspicious user. A proxy replaces that signal with an IP whose classification matches the task.
3What are the three types of proxies?
By IP source: datacenter (hosting provider), residential (consumer ISP), and mobile (carrier-assigned, behind CGNAT). By protocol the split is HTTP, HTTPS and SOCKS5, which is a separate question from where the IP lives.
4How much does a residential proxy cost per month?
There is no single monthly price, because pooled residential and mobile access is billed per gigabyte and your bill depends on traffic. Dedicated and static lines are billed monthly. On the mobile tier, VoidMob's pool starts at $3.99 for 1 GB and falls to $2.50 per GB at the top tier, with dedicated devices from $49 per month by country.
5What are the disadvantages of a proxy?
Higher latency than a direct connection, bandwidth cost, no encryption unless the traffic is already HTTPS, and inherited reputation: you share the IP's history with whoever used it before. Peer-sourced pools add instability, since your exit can vanish when the host device goes offline.
6Does a proxy hide your IP address?
It hides your IP from the target site, which sees the exit IP instead. It does not hide it from the proxy operator, and it does not stop leaks from other layers: WebRTC, DNS, or a browser timezone that contradicts the exit location will expose the mismatch.
Higher trust than residential, same simple setup
Real 4G/5G devices behind carrier NAT: dedicated lines you rotate on demand, or pay-per-GB pools with sticky sessions.