SocksNode

Point a browser profile at SocksNode residential proxies. Three steps, no plugin, no proxy-auth extension.

SocksNode rotating residential proxies: one gateway, rotating and sticky on separate ports, and the country, city and session all encoded in the username. Measured on a live account with AntiBrow, Pool 1, not only read off the docs page - and the sticky ports turned out to need a session token to honour any targeting at all.

https://socksnode.com/en/residential-proxies

1. Get the credentials

In your SocksNode dashboard, open the residential product and copy the gateway host, the port, and the username and password. Everything below assumes those four values.

2. Build the proxy URL

One string, credentials included. Targeting and session options go in whichever half this provider puts them in - the table below says which.

http://<username>-country-us-session-<id>-lifetime-60:<password>@global.socksnode.com:9000

3. Launch

Timezone, locale and WebRTC are derived from the exit address, so a US exit does not arrive with your own timezone attached.

await ab.launch({
  profile: 'acc-01',
  proxy: 'http://<username>-country-us-session-<id>-lifetime-60:<password>@global.socksnode.com:9000',
})

launch(
    profile="acc-01",
    proxy="http://<username>-country-us-session-<id>-lifetime-60:<password>@global.socksnode.com:9000",
)

Prefer not to run an account at all? Managed residential proxies are included on paid plans.

Parameters

Read off SocksNode's own documentation on 2026-10-15. Ports and endpoints differ by plan and by zone, so where this table and your dashboard disagree, the dashboard is right.

Gateway	global.socksnode.com picks the entry nearest you. fr.socksnode.com, us.socksnode.com and sg.socksnode.com are the regional entries; all three resolved and answered a -country-us request on 2026-10-15. The entry only affects latency - the exit country comes from the username.
Ports	9000 HTTP rotating, 10000 HTTP sticky, 11000 SOCKS5 rotating, 12000 SOCKS5 sticky. The dashboard generator prints 10000 for HTTP sticky and 12000 for SOCKS5 sticky, matching the docs table.
Protocols	HTTP and SOCKS5, on different ports. Both were measured in AntiBrow with the same credential.
Options ride in	the username
Country targeting	-country-<iso2>, lowercase, appended to the username. Narrower targets follow it: -state-<full name, no spaces>, -city-<name, no spaces>, -asn-<number>. Measured: -country-de came out on Deutsche Telekom in Hesse, -country-gb on Hyperoptic, -country-jp on KDDI and Chubu Telecom, and -country-us-city-losangeles in Los Angeles on the rotating port.
Sticky session	-session-<id>-lifetime-<minutes> in the username, on a sticky port (10000 or 12000). Measured: one session id returned 38.32.192.170 in two separate AntiBrow launches, and a second id returned a different IP on a different ISP. The session lives per port: the same id on 10000 and 12000 gave two different exits.
Session length	1 to 1440 minutes on Pool 1 and Pool 3, 1 to 60 on Pool 2, per the docs. The generator defaults to 60.
Source	https://socksnode.com/en/docs

Worth knowing

On the sticky ports, always include -session-. Without it, 10000 pinned one exit per account and ignored the rest of the username: -country-us, -country-de and -country-us-city-losangeles all came out on the same Dallas address, in curl and in an AntiBrow profile, and the profile duly took America/Chicago. A German profile set up that way is a Texan one. The dashboard generator adds the session for you; strings assembled by hand are where this bites.
The reverse also fails: a -session- token on a rotating port (9000 or 11000) is not ignored, the gateway aborts the CONNECT with no status code at all. A wrong password, by contrast, comes back as a clean 407 with realm SocksNode. A closed connection with no error usually means a session token on the wrong port.
Measured on 2026-10-15 with AntiBrow, one profile per case on Pool 1: first page in 1.9 to 4.4 seconds, SOCKS5 the slowest. Of 26 distinct exits seen across all runs, 20 sat on consumer ISPs or mobile carriers (Charter, Comcast, RCN, T-Mobile, Deutsche Telekom, Hyperoptic, KDDI and others); 5 were on AS40403 Rocks Computer Services and one on Cogent.
On a sticky session the timezone and the language both followed the exit: Europe/Berlin with de, Europe/London with en-GB, Asia/Tokyo with ja, America/Detroit for a Michigan exit. On a rotating port the exit changes per connection, so the address AntiBrow looked up at launch need not be the one a site sees: one rotating US profile took America/New_York while its next page exited in California. Use a sticky session for any profile that should read as one place.
No WebRTC leak on any run: the host candidate stayed an mDNS .local name and the machine's own address never appeared. The srflx candidate came back through the proxy - on sticky sessions it was the exit address itself, on rotating ports another residential exit.
The credential comes from the dashboard Proxy Generator, and it stays blank until you pick a pool (Pool 1, 2, 3 or Mix). Every value on this page was measured on Pool 1, the default for the API and the one the generator describes as having every targeting option and sticky IPs up to 24 hours. Bandwidth is bought by the GB, does not expire, and works on all pools.