GonzoProxy

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

GonzoProxy residential proxies: one gateway on one port for HTTP, HTTPS and SOCKS5, with country, region, city, ISP and sticky session all written into the username by the dashboard's Proxy Generator. Measured on a live account, not only read off the docs.

1. Get the credentials

In your GonzoProxy 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://<login>_c_US_s_<session>_ttl_30m:<password>@connect.gonzoproxy.app:10000

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://<login>_c_US_s_<session>_ttl_30m:<password>@connect.gonzoproxy.app:10000',
})

launch(
    profile="acc-01",
    proxy="http://<login>_c_US_s_<session>_ttl_30m:<password>@connect.gonzoproxy.app:10000",
)

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

Parameters

Read off GonzoProxy'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	connect.gonzoproxy.app. The generator's Server dropdown swaps in eu.connect.gonzoproxy.app, asia.connect.gonzoproxy.app or us.connect.gonzoproxy.app; per the docs that picks the gateway region only, and the exit country still comes from the username. A German exit through eu. and a Japanese one through asia. were measured and worked.
Ports	10000 for every protocol, as printed by the generator and stated in the docs.
Protocols	HTTP, HTTPS and SOCKS5, same host and port. All three were measured in AntiBrow. The HTTPS mode is real TLS to the proxy, and its certificate passed curl's normal verification. Per the docs, SOCKS4 does not work.
Options ride in	the username
Country targeting	_c_<ISO2> after your login. Narrower targets are _sd_<region id>, _city_<City-Name> and _isp_<provider id>. Region and provider are numeric ids, not names (California is sd_443), so pick them in the generator and copy the string. _c_US_sd_443_city_Los-Angeles came out in Los Angeles; _c_DE and _c_JP came out in Germany and Japan.
Sticky session	_s_<id>_ttl_<n><s\|m\|h>, both or neither. The generator defaults to Sticky with _ttl_72h and a random id; switching Rotation to Randomize IP drops both segments. Your own lowercase id works too. Measured: two different session ids each returned the same exit across two separate browser launches, and a different id gave a different exit.
Session length	Up to 7 days (168 hours), set in seconds, minutes or hours. The docs call it an upper bound: in GonzoProxy's own test 51 of 90 sticky sessions kept their address over 84 minutes.
Source	https://help.gonzoproxy.com/instructions/gonzoproxy-residential-proxies

Worth knowing

Measured on 2026-10-15 with AntiBrow, one profile per case: US exits on Charter, Comcast and regional ISPs (REV, Smithville), German ones on Deutsche Telekom, Vodafone and M-net, Japanese ones on transix and Chubu Telecom. Every exit looked up sat on a consumer ISP. Launch took 6.8 to 10.5 seconds, the first page 1.5 to 2.4 seconds, ipinfo.io 1.5 to 2.9 seconds.
Use a sticky session for a browser profile. Without one the exit changes per connection: the launch-time geo lookup, the first page and the second page saw three different addresses. The profile takes its timezone from the launch lookup, so in rotating mode it can disagree with the page exit - one US run set America/Chicago while the pages exited in New Mexico. With a session, launch lookup, pages and timezone all matched.
A sticky session can still move. One of the three sticky ids tested in the browser landed on a different exit between the launch lookup and the first page, seconds apart, so that profile's timezone came from the first address. The docs say the same thing: the address lives as long as the device behind it stays online. If the exit has to be exact, check browser.public_ip against the page after launch.
Timezone and language both followed the exit: America/Los_Angeles with en-US for Los Angeles, Europe/Berlin with de for Germany, Asia/Tokyo with ja for Japan.
No WebRTC leak on any run: the host candidate was an mDNS .local name, and the srflx candidate carried the address from the launch lookup, never the machine's own address. With a sticky session that address was the page exit itself. One rotating launch got an IPv6 exit, and the srflx candidate was that IPv6 address.
Take the host from the generator, not from older blog posts: a GonzoProxy setup post still gives pool.gonzoproxy.com port 1000, and on 2026-10-15 that name resolved to 127.0.0.1. A wrong password comes back as a clean 407.
Per the docs, financial websites are closed through the pool by default, and since July 2026 they are not opened for anyone, KYC or not. Traffic is sold per GB and does not expire; the docs list crypto via Cryptomus as the only payment method since July 2026. The account tested held 3 GB credited by GonzoProxy.