Proxy chaining means sending your traffic through two or more proxy servers in a row, so each hop only talks to the one before it and the one after it, and the website sees only the last proxy’s IP address. It adds a layer of separation between you and the site, at the cost of speed and reliability. This guide explains how proxy chaining works, how a proxy chain differs from rotation and from Tor, how to build one with proxychains and Proxifier, and when a single good residential proxy is the better choice.
The short version
A proxy chain routes one connection through several proxies in sequence: you connect to proxy 1, proxy 1 connects to proxy 2, and the last proxy connects to the website. No single proxy sees both who you are and where you are going, unless it is the first or last hop and can see more than the rest. Chaining makes every request slower, and each extra hop is one more thing that can fail, so use it when separation matters more than speed.
What is proxy chaining?
Several proxies, one after anotherA single proxy sits between you and a website: you connect to the proxy, and the proxy connects to the site. Proxy chaining puts more proxies in that line. You connect to the first proxy, which connects to the second, which connects to the third, and only the last one, the exit, talks to the website. The site sees the exit proxy’s IP address. The first proxy sees your IP address but not the final destination if the next hop hides it. The proxies in the middle see only their neighbours.
People also call this a proxy chain, a chained proxy or, after the most common Linux tool, proxychains. The idea is the same in every case: spread what can be learned about a connection across several independent operators, so no single one of them holds the whole picture.
Key takeaways
- Proxy chaining sends one connection through two or more proxies in sequence.
- The website sees only the exit proxy’s IP; the entry proxy sees yours.
- Every hop adds latency and a new point of failure.
- Chaining is not rotation: rotation changes the exit IP between requests, chaining adds hops to each request.
- HTTPS still protects the content end to end; the proxies relay encrypted bytes.
How a proxy chain works
Tunnels inside tunnelsChains are built from proxies that can open a raw tunnel to another host: SOCKS proxies, defined for version 5 in RFC 1928, and HTTP proxies that support the CONNECT method in RFC 9110. The client asks the first proxy to open a tunnel to the second proxy. Inside that tunnel it asks the second proxy to open a tunnel to the third, and so on, until the last proxy opens a tunnel to the website.
your computer (your IP)
| tunnel 1: "connect me to proxy B"
v
proxy A (entry: sees your IP, sees proxy B)
| tunnel 2, inside tunnel 1: "connect me to proxy C"
v
proxy B (middle: sees proxy A and proxy C only)
| tunnel 3: "connect me to example.com:443"
v
proxy C (exit: sees proxy B and the website)
|
v
example.com --> sees proxy C's IP
Because each tunnel is opened through the previous one, an intermediate proxy passes along bytes it can’t make sense of beyond the next address. The encryption that protects a web page is a separate layer: with HTTPS, your browser and the website negotiate TLS end to end, so no proxy in the chain can read the page, whichever hop it is.
DNS is the part people forget. If your computer resolves the website’s name itself, the lookup leaves outside the chain and reveals where you are going. Tools that support proxy chaining usually offer a setting to send name lookups through the chain; proxychains calls it proxy_dns.
Proxy chaining vs rotation vs Tor
Three different ideas that get mixed up| Proxy chain | Rotating proxy | Tor | |
|---|---|---|---|
| What it does | Adds hops to each connection | Changes the exit IP between requests | Routes through three volunteer relays |
| Who runs the hops | Whoever you choose | One provider’s gateway and IP pool | Volunteers on the Tor network |
| Exit IP | The last proxy you picked | A residential, mobile or datacenter IP from the pool | A public Tor exit relay |
| Speed | Slower with every hop | One hop, fast | Slow, varies |
| Typical use | Separation between operators, testing | Scraping, geo-testing, account work | Anonymous browsing |
Tor is itself a kind of chain. The Tor Project describes a circuit as you, then a guard relay, a middle relay and an exit relay, with the destination seeing the exit relay’s IP address. The difference from a proxy chain you build yourself is who runs the hops and how the path is chosen: Tor picks volunteer relays for you and encrypts each layer, while a proxy chain uses the proxies you configure.
Rotation solves a different problem. A backconnect gateway gives you one address to connect to and changes the IP behind it on every request or session. That spreads many requests over many IPs, which is what scraping and price monitoring need, without adding any hops.
Proxy chaining with proxychains
The standard tool on Linux and macOSproxychains-ng is an open-source tool that forces a program’s connections through a list of proxies. Its documentation says it hooks the network functions of dynamically linked programs and redirects their connections through SOCKS4a, SOCKS5 or HTTP proxies, with a username and password where the proxy needs one. It runs on Linux, BSD, macOS and Haiku.
You list the proxies in its configuration file, proxychains.conf, one per line, in the order the chain should use them, and choose how the list is treated:
- strict_chain: use every proxy, in the listed order. If one is down, the connection fails.
- dynamic_chain: use the proxies in order but skip ones that don’t answer.
- random_chain: build each chain from a random selection of the list, with a length you set in
chain_len. - proxy_dns: send name lookups through the chain instead of your own resolver.
strict_chain
proxy_dns
[ProxyList]
# type ip port user pass
socks5 192.0.2.10 1080
socks5 198.51.100.20 1080 myuser mypassword
Then prefix any command with proxychains4, for example proxychains4 curl https://example.com, and its connections go through both proxies in turn. The configuration format expects each proxy’s IP address, and the last line is the exit your target sees, so that is where a residential or mobile proxy belongs if the site should see a household or phone connection.
Proxy chains in Proxifier and SSH
Windows, macOS and admin toolsProxifier is a desktop app for Windows and macOS that routes other programs through proxies. Its documentation explains how to add two or more proxies under Proxy Servers, create a chain and drag the proxies into it; connections pass through them from the top of the list to the bottom. You then point a rule at the chain, so only the apps you choose use it. Our Proxifier guide covers the basic setup with ProxyEmpire.
SSH can chain jump hosts natively. OpenSSH’s -J option connects to the target by first connecting to a jump host, and several jump hosts can be listed, separated by commas. That is a common way for administrators to reach servers on a private network through a bastion host, and it is a form of proxy chaining at the SSH layer.
Pros and cons of proxy chaining
Separation has a price| Pros | Cons |
|---|---|
| No single operator sees both your IP and your destination | Every hop adds latency, so pages and requests are slower |
| You can mix proxy types, such as a private entry and a residential exit | More hops mean more ways for a connection to fail |
| Useful for testing how systems behave behind layered proxies | Hard to debug: an error can come from any hop |
| Works with standard SOCKS5 and HTTP CONNECT proxies | Doesn’t add encryption by itself, and a free proxy anywhere in the chain is a risk |
The last point matters. A chain is only as trustworthy as its entry and exit. A free public proxy as the exit can see and alter unencrypted traffic, and as the entry it sees your real IP. Use proxies you control or pay for, and keep everything you send over HTTPS.
When to use a proxy chain
And when one proxy is enough- Authorised security testing. Penetration testers and red teams use proxy chains, with written permission, to test how a network handles traffic from layered sources.
- Reaching private networks. Administrators chain jump hosts to reach servers that aren’t exposed to the internet.
- Separation between operators. A private entry proxy you run, followed by a commercial residential exit, keeps your own IP away from the proxy provider as well as the website.
- Testing layered set-ups. Developers check how an app behaves behind corporate proxies and gateways.
For most business work, proxy chaining is unnecessary. Web scraping, price monitoring, SEO checks and account management need one reliable exit IP in the right country, rotated or kept sticky as the job requires. A single residential or mobile proxy does that with less latency and fewer failures than any chain.
Where ProxyEmpire fits
A clean exit, or the only hop you needProxyEmpire’s proxies work over HTTP, HTTPS and SOCKS5 with a username and password, so they can sit at the end of a chain in proxychains or Proxifier as the exit your target sees: a residential IP from 30M+ in 179 countries and territories, or a 4G/5G mobile IP from 4M+ in 174, with city, ISP and ASN targeting at no extra charge. For most jobs you won’t need a chain at all: one ProxyEmpire gateway gives you rotating or sticky exits directly, with 99.9% uptime shown on the public status page and 24/7 support from real people. Residential starts at $3.50/GB and falls to $1.50/GB, and you can test it with a $1.97 trial.
Proxy chaining FAQ
Short answersWhat is proxy chaining in simple terms?
Connecting through several proxies one after another, so the website only sees the last proxy’s IP and no single proxy sees the whole path.
Is proxy chaining the same as a VPN?
No. A VPN is one encrypted tunnel from your device to one server. A proxy chain is several proxy hops in a row, and it doesn’t add encryption unless the traffic is already encrypted, such as HTTPS.
How many proxies should a chain have?
Two or three at most for practical use. Each extra hop adds delay and another chance of failure without much extra benefit.
Does proxy chaining make me anonymous?
It makes you harder to trace, but not invisible. Browser fingerprints, cookies, logins and DNS leaks can still identify you, and the entry proxy still sees your IP.
What is proxychains?
proxychains-ng is an open-source tool for Linux, BSD and macOS that forces a program’s connections through a list of SOCKS or HTTP proxies, in strict, dynamic or random order.
Can I use proxy chaining on Windows?
Yes, with an app such as Proxifier, which supports proxy chains, or with SSH jump hosts. proxychains-ng itself doesn’t list Windows among its supported systems.
Is proxy chaining legal?
Using proxies and chaining them is legal in most places. What you do through them still has to follow the law and each site’s terms.
Do I need a proxy chain for web scraping?
Usually not. Scraping needs many IPs and the right locations, which a rotating residential proxy provides in a single hop with far less latency.
References
Primary documentation- proxychains-ng — README and configuration. github.com/rofl0r/proxychains-ng
- Proxifier — Proxy Chains. proxifier.com/docs/win-v4/chain.html
- OpenBSD — ssh(1) manual, the -J option. man.openbsd.org/ssh
- Tor Project — Types of relays on the Tor network. community.torproject.org/relay/types-of-relays
- IETF — RFC 1928, “SOCKS Protocol Version 5”. rfc-editor.org/rfc/rfc1928
- IETF — RFC 9110, “HTTP Semantics”, the CONNECT method. rfc-editor.org/rfc/rfc9110
One clean exit IP, with or without a chain
Residential and mobile proxies over HTTP, HTTPS and SOCKS5, with city, ISP and ASN targeting at no extra charge, rotating or sticky sessions and 24/7 support from real people. Try ProxyEmpire for $1.97.



