Web Unlocker vs Residential Proxy vs Mobile Proxy: When You Need Which

We fetched the same URLs from a datacenter server, through a plain residential proxy and through a web unlocker. Some sites needed nothing, some only needed a residential IP, and some only opened for the unlocker. Here is what each layer fixes, and where the mobile tier fits.

A residential proxy changes where your request comes from. A web unlocker also changes what the request looks like: it sends it under a real browser TLS fingerprint, retries on fresh IPs and runs a headless browser when a JavaScript challenge appears. You need the unlocker only when a clean residential IP still gets blocked. Otherwise the proxy is enough.

That is the theory. To check it, we fetched the same URLs three ways on 29 September 2026 and kept the results site by site. Some pages needed nothing at all, some only needed a residential IP, and some only opened for the unlocker. The tables below show which was which.

• No proxy needed: docs.python.org, books.toscrape.com, Hacker News, Wikipedia and GitHub answered a plain request from a datacenter server.
• A residential proxy was enough: Zillow and Leboncoin blocked the datacenter server but served the real page through a plain residential proxy.
• Only the unlocker got through: Indeed, Glassdoor, Walmart and Best Buy refused both plain clients and returned the page through the unlocker.

How we tested

Each URL was fetched three ways on 29 September 2026. First, plain curl from a datacenter server in Frankfurt with a Chrome User-Agent. Second, the same plain curl through a QuantumProxies.io residential proxy with a US exit (a French exit for Leboncoin). Third, through the Web Unlocker forward proxy on the residential tier, with the same exit country. The status is the final HTTP status the client saw. Times are wall-clock for one unlocker request.

What each layer fixes

A modern bot wall checks several things before it sends a page, and each tool fixes a different subset. Knowing which wall you are hitting tells you what to buy.

The first row is where most scrapers start and where a residential proxy earns its price. Hosting ranges are easy to recognise, and many sites refuse them outright. The second row is why a clean IP is sometimes not enough: the TLS handshake of curl, Python or Node looks nothing like Chrome's, and Cloudflare documents JA3/JA4 fingerprints as a way to identify clients by exactly that. Our guide to TLS fingerprinting covers it in depth. The third row needs a real JavaScript engine.

Sites that needed no proxy at all

Start here, because it is the cheapest outcome. These pages answered a plain request from a datacenter server. Sending them through anything else costs money and adds latency for no gain.

The BBC 302 is a redirect, not a block. Our test client did not follow redirects, and any client that does lands on the page.

Where a plain residential proxy was enough

Zillow and Leboncoin are the case a residential proxy was built for. The datacenter IP was refused, and the same request from a home IP got the page. The unlocker also worked, but it added nothing you needed.

Amazon is the cautionary row. Both plain clients got the product page on this run, yet the unlocker needed two attempts and a browser before it returned, and took 10.2 seconds. The unlocker bills every byte it moves, retries and browser loads included. On a page that did not need it, you pay for that extra work. This is one request on one day, so do not read it as a rule about Amazon. Read it as a rule about testing plain first.

Where only the web unlocker got through

Here the residential IP alone did not help. Walmart, Best Buy and Indeed returned the real page on the unlocker's first TLS attempt, without a browser. Still, the plain residential column already had a clean home IP and failed, and the obvious remaining difference is what the request looked like. Glassdoor went further: it wanted JavaScript, so the unlocker needed two TLS attempts and then a headless browser, which is why it took 17.2 seconds.

Walmart needs a caveat of its own. We did not record where its 307 redirect pointed. We only know that neither plain client received the results page and the unlocker did.

Use the Web Unlocker on residential exits

Where the mobile tier fits

Mobile carriers put many phones behind each public IP (carrier-grade NAT), so a site that blocks a carrier address risks blocking real customers with it. That is why carrier IPs tend to carry more trust than residential ranges. We explain the mechanism in why mobile proxies are trusted: CGNAT.

The Web Unlocker has a Mobile tier that runs the same logic (browser fingerprints, retries, browser escalation, block reporting) on 4G/5G carrier exits. You select it with -tier-mobile in the proxy username, or "tier": "mobile" on the REST endpoint. It has its own prepaid GB balance. It is meant for sites that refuse residential ranges too, which is exactly what an access_denied block on the residential tier suggests.

A cost-aware escalation ladder in Python

The tables point to one rule: climb only as far as the site forces you to. This function tries each rung in order and stops at the first one that returns a real page. It moves to the Mobile tier only when the residential tier reports an access_denied block. HEADERS and looks_blocked() are the helpers from our web unlocker API tutorial in Python.

import os
import requests
import urllib3

urllib3.disable_warnings(urllib3.exceptions.InsecureRequestWarning)

RESIDENTIAL = os.environ["QP_RESIDENTIAL_PROXY"]   # http://USER:PASS@HOST:PORT from your residential plan
UNLOCK_USER = os.environ["QP_UNLOCK_USER"]         # unlock-XXXXXXXX
UNLOCK_PASS = os.environ["QP_UNLOCK_PASSWORD"]


def unlocker(extra: str = "") -> dict:
    u = f"http://{UNLOCK_USER}-country-us{extra}:{UNLOCK_PASS}@unlock.quantumproxies.io:9000"
    return {"http": u, "https": u}


LADDER = [
    # name,              proxies,                                      verify, timeout
    ("plain",            {},                                           True,   30),
    ("residential",      {"http": RESIDENTIAL, "https": RESIDENTIAL},  True,   30),
    ("unlocker",         unlocker(),                                   False, 120),
    ("unlocker-mobile",  unlocker("-tier-mobile"),                     False, 120),
]


def climb(url: str):
    last = None
    for name, proxies, verify, timeout in LADDER:
        try:
            r = requests.get(url, headers=HEADERS, proxies=proxies, verify=verify, timeout=timeout)
        except requests.RequestException:
            continue                        # no response at all counts as a block
        last = r
        if not name.startswith("unlocker"):
            if not looks_blocked(r):
                return name, r
            continue
        if "x-qp-unlocker-blocked" not in r.headers:
            return name, r
        if r.headers.get("x-qp-block-class") != "access_denied":
            break                           # a different IP will not fix this wall
    return "blocked", last

In production, remember the rung per domain once you know it, so you do not pay for the failed rungs on every request. The unlocker may also send an x-qp-hint header with a suggestion, which is worth logging next to the block class.

How to decide, in five questions

1. Does a plain request from your server return the real page? Then you need neither. Stop there.
2. Does it fail from a datacenter IP but work from a residential one? Buy residential proxies and keep your own client.
3. Does it still fail from a clean residential IP, with a 403, a 'Just a moment' or 'Enable JavaScript' page, or a dropped connection? That is the unlocker's job.
4. Does the unlocker report access_denied on residential exits? Test the Mobile tier on that site before committing volume.

Frequently asked questions

Should I buy residential proxies or use a web unlocker?

Test your targets first. If a plain request from a residential IP returns the real page, as Zillow and Leboncoin did in our 29 September 2026 test, residential proxies are enough and cheaper to run. If a clean residential IP still gets a 403 or a JavaScript challenge, as Indeed and Glassdoor did, you need the unlocker.

Do I need residential proxies, or would any proxy work?

It depends on the site. Wikipedia, GitHub and Hacker News answered a plain datacenter request in our test, so no proxy was needed. Zillow and Leboncoin refused the datacenter IP and accepted a residential one. Datacenter proxies share the first problem, because hosting ranges are easy for sites to recognise and refuse.

Are mobile proxies more reliable than residential proxies for web scraping?

Carrier IPs are shared by many phones through CGNAT, so sites are more reluctant to block them, and that helps against IP-reputation blocks. They do not change your TLS fingerprint or solve JavaScript challenges on their own.

Do mobile proxies reduce captchas?

They can reduce captchas that are triggered by IP reputation, because a carrier address looks like many ordinary phone users.

How is the web unlocker billed compared with a residential proxy?

Both are billed per GB. The unlocker counts every byte it moves on your behalf, including retries, blocked pages and the browser's page load, and it uses its own prepaid balance per tier: residential exits and mobile carrier exits. The current price per GB is shown in the dashboard.

Residential proxies fix where a request comes from. The web unlocker also fixes what it looks like and whether it can run JavaScript. The Mobile tier changes the IP again for sites that refuse residential ranges. Buy the lowest rung your targets accept, and let the block class tell you when to climb.

Compare the Web Unlocker tiers

Targets that refuse residential ranges? See the Web Unlocker on mobile exits.