Skip to content
residential proxiessticky sessionsanti-bot

Why your residential proxy still gets blocked on Akamai and Cloudflare sites

A residential exit can be clean and still meet a block page. The address, the TLS handshake, and the challenge script are three separate checks.

A residential proxy puts a normal ISP address on the request. Akamai and Cloudflare still read the handshake, the headers, and a script in the page. When those disagree, a second residential IP returns the block you already have.

The address is one check. This page is the other two, and the point where a solver belongs.

The page you are looking at

Read the body once before you change the proxy line.

A flat page that says "Unusual Traffic Detected", and has no script, is Akamai judging the request in front of it. The handshake and the headers already lost. A new exit repeats that judgment.

HTML with a script address ending in ?v= and a UUID is Akamai SBSD. A browser would run that script and post the answer. Akamai then sets bm_s, bm_sc, and bm_so. The Akamai SBSD solver takes the script and returns the payload. You post that payload yourself, from the session that downloaded the script. The proxy stays on your client the whole way.

A Cloudflare HTML page waiting on cf_clearance is JavaScript Detections. A script in the page is supposed to run, and a visitor who passes receives that cookie. The Cloudflare JSD solver runs the exchange through your proxy and returns the cookie with the user agent it belongs to.

Two other Cloudflare screens get filed under the same name. Turnstile is a widget on a form. It returns a token. The managed challenge is the interstitial that tells the browser to wait. A JavaScript Detections solve leaves both of them in place.

What the address is scored on

The site can see the exit, and it scores the network that exit belongs to.

The origin ASN is the network announcing the prefix. A hosting range and a residential range are different scores. The IP lookup shows the address, the network, and the reverse name for the exit you just used.

Geography is the country code on the username. A United States session belongs on us.proxylabs.app:8080. A United Kingdom session uses -country-gb on eu.proxylabs.app:8080. The gateway follows that code. The map is in How to Connect a ProxyLabs Residential Proxy.

Rate limits sit on the address as well. One sticky exit gathers every request you send through it. A rotating pool spreads that count, and it drops the cookie the site just issued. Rotating vs Sticky Proxies is the choice between those two.

What rides on the client

The proxy forwards the bytes your client already built.

Stock Node, Python requests, and Go's net/http each send their own ClientHello. A Chrome user agent on that handshake is two claims at once, and the comparison happens before any HTML exists. JA4+ TLS Fingerprinting is how those handshakes are summarized. tls-client is a client that can present a browser handshake through the proxy.

Header order, HTTP/2 pseudo-headers, and sec-ch-ua have to name the same browser as the user agent. A copied user agent on a library's default list is still the library. The sequences are in HTTP Header Order.

The challenge script is the part a stock client never runs. That work belongs to a browser, or to a solver. notabot is the solver API for this step. The page you received decides which call to make. Your proxy remains the address the site already scored.

Three pieces, one session

Use them in this order. ProxyLabs does not publish a pass rate for a target missing one of them.

  1. A residential exit, held on a sticky session for the whole job.
  2. A client whose TLS handshake and headers match the user agent you send.
  3. A solver when the body is a challenge script you are leaving unexecuted.

SBSD stays on your machine. The script download, the payload post, and the retry share one cookie jar, one user agent, and one TLS fingerprint. JavaScript Detections is the other shape. The solver earns cf_clearance through the proxy you pass in. Later requests stay on that proxy, and they send the user agent that came back with the cookie.

A second residential address repairs a bad ASN. It leaves a library handshake where it was. A solver leaves a hosting range where it was.

The sticky session is the thread

The cookie is good for the address that earned it. A rotating username takes a new exit on the next request. cf_clearance then names an address you have left. SBSD cookies were set on the session that fetched the script. A new exit between that fetch and the post is a different session, and the payload was built for the old one.

Pick the length before the first request. Residential sticky time is 10, 30, 60, or 120 minutes. The dashboard writes that length in seconds. The clock starts when the session starts. Sending the same session id again does not move it.

MinutesSeconds in the username
10600
301800
603600
1207200

A 60-minute United States session:

text
http://user-country-us-ttl-3600-session-a1b2c3:[email protected]:8080

a1b2c3 stands in for the six-character id the dashboard generates. When the challenge and the pages after it can run past 30 minutes, start at 60 or 120. Paste the line from the dashboard once the request leaves a notebook.

When it is still blocked

Stop at the first item that fails.

  • A second request with the same session id returns the same address, and the country matches the username. How to test a proxy is that check.
  • The TTL was set before the first request, and it covers the pages you still have to fetch.
  • The handshake matches the user agent. sec-ch-ua and the header order belong to that same client.
  • The body matches the solver you called. ?v= plus a UUID is SBSD. cf_clearance is JavaScript Detections. A Turnstile widget or a wait interstitial is a different product, and the solvers above leave it untouched.
  • The requests after the challenge keep the same proxy, the same user agent, and the cookies from that session.

When those five hold and the body is still the challenge script, another residential IP repeats the page. The address has already been accepted as an address. The open item is the script. Session lengths and the public residential price are on residential proxies.

Useful guide? Share it with your team.

Share
← Back to all articlesBack to top ↑
All articles ↗
residential proxies

How to Connect a ProxyLabs Residential Proxy

The residential gateways, username order, and sticky lengths ProxyLabs actually uses. Copy the finished string from your dashboard.

4 min read
proxies

Rotating vs Sticky Proxies: When to Use Each

Sticky vs rotating proxies: a new address on each request, or the same address for 10, 30, 60, or 120 minutes. When to use each on ProxyLabs.

8 min read
proxy testing

How to Test a Proxy Before You Pay

A repeatable proxy test: connectivity, exit country, sticky lifetime, and the fingerprint. No provider success rate required.

7 min read