Exit node
The last hop in a proxy chain, the address the destination site actually sees, as opposed to the gateway you connect to.
The exit node is where your traffic leaves the proxy network and rejoins the open internet. It is the address the destination actually records, which makes it the one that decides everything a site infers about you: which country you appear to be in, what kind of network you appear to be on, and what reputation you arrive carrying.
The address you connected TO is a separate thing entirely, and keeping the two apart is the whole point of the term. You dial a gateway, and the gateway arranges an exit on your behalf. The destination never sees the gateway. It has no idea one exists.
In a rotating setup the gateway stays fixed while the exit changes underneath it, which is exactly why one unchanged line of configuration can present as thousands of different visitors. In a static or sticky setup the exit holds still for a while. Either way, when you ask what country your traffic carries, you are asking about the exit and never about the entry.
This is the most common source of confused testing we see, and it produces a very specific wrong conclusion. Someone looks up the gateway hostname, sees it geolocate to wherever the provider's infrastructure sits, and concludes the country targeting is broken. It is not: they measured the door instead of the destination.
The correct test is to ask the internet what it saw. Send a request through the proxy to any service that echoes back the address it observed, and whatever comes back is your exit. That is the address every site you contact will judge, and it is the only one worth checking.
One consequence worth carrying: because the exit is what is seen, it is also what accumulates reputation. Any consequence of your behaviour lands on the exit, not on the gateway, which is why a rotating pool spreads the cost of a mistake across many addresses and a static exit absorbs all of it.
How it works
- 1.You configure one gateway host and port, and never change it.
- 2.Your client connects there and authenticates, with any targeting expressed in the credentials.
- 3.The gateway selects an exit matching what you asked for, by country, city or session.
- 4.The exit opens the connection to your destination and relays the traffic.
- 5.The destination logs the EXIT address and judges the request on that.
- 6.On the next request the gateway may hand you a different exit, unless a sticky session pinned the current one.
Frequently asked questions
How do I find out what my exit IP is?
Send a request through the proxy to any endpoint that echoes back the address it received, and read the answer. That is your exit. Looking up the gateway hostname you configured tells you nothing about it, because the destination never sees the gateway at all.
Why does my exit IP geolocate to the wrong country?
First check that you measured the exit rather than the gateway, which accounts for most reports of this. If the exit really is in the wrong country, either the pool could not fill your request and fell back to a nearby one, or the geolocation database is simply out of date for that address, which is common with recently reassigned ranges. Testing several exits distinguishes a pool problem from a database problem.
Does the exit node see my traffic?
It relays every byte, so it sees whatever is not already encrypted. HTTPS means the operator sees the destination hostname, the timing and the volume, but not the contents. On a plain HTTP connection it can see everything. This is the reason the operator's identity matters, and the reason free public proxies are a poor idea for anything sensitive.
Can I keep the same exit node?
Yes, by asking for it rather than hoping. A sticky session pins one exit for a defined window, and a static or ISP proxy assigns one for as long as you hold it. On residential supply neither is an absolute guarantee, because the exit is somebody's home connection and it can end regardless of the window you requested.
Back to the full glossary.