Proxy Chains Explained: Bouncing Through Multiple Proxies
One proxy hides your IP from the website. But it still knows two things: who you are, and where you're going. A proxy chain splits that knowledge in two. Your traffic bounces through two or more proxies in a row, so no single server sees the whole trip. Here's how to build one, what it costs in speed, and when it's not worth it.

What a proxy chain actually is
With a normal proxy, the path is short: you connect to the proxy, the proxy connects to the website. That one server sees your real IP and the site you asked for. If you'd rather not hand one stranger the full picture, that's the problem a chain solves.
A proxy chain adds a second middleman: you connect to proxy A, proxy A connects to proxy B, and proxy B connects to the website. Proxy A knows who you are, not where you're going. Proxy B knows the destination, not who you are. The website only ever sees proxy B. I used to think more hops meant more safety, until I measured a chain. The numbers are below.
How a chain works
Each hop opens a tunnel to the next one. That means SOCKS5 proxies, or HTTP proxies that support CONNECT.
- Entry: sees your real IP and the next hop, never the website.
- Middle: sees only its two neighbours.
- Exit: sees the website and the proxy before it, never your real IP.
- The website: sees only the exit proxy's IP.
Chaining adds no encryption. Each hop can still read whatever isn't protected by HTTPS. The chain hides the path, not the content.

Prefer watching? This walkthrough shows the setup on screen.
Build a 2-hop chain
Two hops is the sweet spot. One hop is just a normal proxy, and three or more hops on free proxies usually fall over before they load a page. Here's the Linux setup.
Step 1: Pick two live SOCKS5 proxies
Open the proxy list, filter by SOCKS5, and pick two entries with low latency and a recent green check. Test each one alone with our Proxy Checker first. I used two entries off today's list: 128.199.202.122:1080 (Singapore) and 161.35.70.249:1080 (Germany).
Step 2: Install proxychains
On Ubuntu or Debian:
sudo apt update
sudo apt install proxychains4 -y
On macOS, it's brew install proxychains-ng. Windows users can use Proxifier instead.
Step 3: Edit the config file
Open /etc/proxychains4.conf, uncomment dynamic_chain, and leave strict_chain commented out. Then scroll to [ProxyList] and add your two proxies in order:
dynamic_chain
proxy_dns
[ProxyList]
socks5 128.199.202.122 1080
socks5 161.35.70.249 1080
The order matters: the first line is the entry hop that sees your IP, the last line is the exit the website sees. Keep proxy_dns enabled, or your DNS lookups leak outside the chain.
Step 4: Run something through it and verify
Prefix any command with proxychains4:
proxychains4 curl https://httpbin.org/ip
The IP it prints back should be your exit proxy's IP, not yours. If it prints your real IP, the chain didn't engage, so double-check the config.
What I measured
Guides say "each hop adds latency" and leave it there. I wanted real numbers. One caveat: I couldn't run a live chain end to end from this machine, because its network blocks outbound proxy connections. What I could measure is the direct request, and the two hops' tested latencies straight off today's list:
- Direct, no proxy: 0.66 seconds, timed with curl to httpbin.org.
- Hop 1 alone (Singapore, 128.199.202.122:1080): 258 ms tested latency on today's proxy list.
- Hop 2 alone (Germany, 161.35.70.249:1080): 403 ms tested latency.
Now do the chain math. A request through both hops pays both latencies: 258 + 403 = 661 ms of proxy delay before the target site even starts responding. That is already as long as the whole direct request, and a real chain adds connection setup at each hop on top. So a 2-hop chain costs roughly double the direct time at minimum. Two hops, max, on free proxies.

Strict, dynamic, or random
- strict_chain: uses every proxy in the order you listed. One dead hop kills the connection.
- dynamic_chain: uses the proxies in order but skips any that don't answer. The only sane choice for a free list.
- random_chain: picks a random set from your list for each connection.
If you're chaining free proxies and you're not on dynamic_chain, you're signing up for random failures.
Chains vs rotation vs Tor
Rotation changes your exit IP between requests. Chaining keeps the same exit IP but adds hops, so no single proxy sees the whole path. If rotation is what you need, our guide What Is a Rotating Proxy and Do You Need One? covers it.
Tor is the comparison that matters most. It routes you through three volunteer relays with encryption layered at every hop, and no relay knows both ends. A home-made chain is a rough sketch of that idea with the encryption layer missing. If you genuinely need anonymity, use Tor. Proxychains-ng is open about its limits: it hooks network calls in dynamically linked programs and routes TCP only, so statically linked programs and UDP traffic bypass it. The proxychains-ng README on GitHub states both limits plainly.
When a chain is a bad idea
Here's where I wouldn't use one:
- Logging in anywhere: never chain into a bank, email, or any account that matters. Every hop is another stranger who could log the traffic. Never use free proxies for banking.
- Anything speed-sensitive: gaming, video calls, live streams. The extra hops add delay you'll feel right away.
- When the exit IP is blocked: a chain doesn't unblock anything. The website judges the exit IP. Pick a different exit from the locations page instead.
- More than two or three hops: past two hops the gain is tiny and the failure rate climbs. If two hops don't solve it, use a different tool, not a longer chain.
My chain keeps breaking
- It worked, then stopped: one hop died. Test each hop alone with the Proxy Checker.
- It's slow: check each hop's latency on the proxy list and swap out the slowest. A chain is only as fast as its slowest hop.
- The site still sees my real IP: your DNS is leaking outside the chain. Enable proxy_dns, then run our VPN Leak Test.
- One program ignores the chain: proxychains only hooks dynamically linked programs and TCP traffic. A statically linked binary or anything using UDP bypasses it silently.
So, should you chain?
For most people: no. One good proxy, tested properly, does the job with half the delay and half the failures. Our proxy testing guide shows how to pick one in five minutes. But if you don't want any single proxy operator to see both who you are and where you're going, a 2-hop chain with two tested SOCKS5 proxies on dynamic_chain is the honest, working answer. Build it, time it, verify the exit IP, and if it's too slow, drop back to one.
Comments
Loading comments…
Leave a comment