How to Check a Proxy's Exit IP

Measure the exit IP at the destination. The address in a proxy list is the listener your client contacts; NAT, routing or another outbound hop can give the destination a different source address.

Compare the same IP-check endpoint with and without the proxy. For a quick public example:

curl --noproxy '*' --connect-timeout 5 --max-time 15 https://httpbin.org/ip
curl --proxy http://203.0.113.10:8080 --noproxy '' --connect-timeout 5 --max-time 15 https://httpbin.org/ip

Replace the documentation proxy address with your live endpoint; for an HTTP entry from the HTTP proxy list, keep its listener address and the observed exit address separate. The first request bypasses proxies, where direct access is allowed; the second clears bypass rules and selects the proxy. The checker receives both requests, so omit private payloads, cookies and tokens.

Inspect the reported address rather than just HTTP 200. A different expected address supports the route used for this request. If both results match, inspect bypass rules and configuration before concluding that the list entry is false.

Check what the IP checker measures

httpbin's origin result can use X-Forwarded-For when present. It can contain a chain rather than a raw socket-peer address, particularly relevant to plain HTTP forwarding tests. A checker you control is preferable when precision matters: record the actual connection peer at a known network boundary and trust forwarding headers only when your infrastructure provides and validates them.

The number curl already knows

curl --proxy http://203.0.113.10:8080 --noproxy '' --output /dev/null --write-out 'peer=%{remote_ip}\n' https://example.com/

remote_ip identifies curl's connection peer, normally the HTTP proxy endpoint in this example. It helps confirm where curl connected but does not observe the proxy's outbound source address. The destination-side result answers that second question.

Repeat the check inside the application that will use the proxy. A successful curl request does not configure a browser; profiles, extensions, bypass rules and apps that ignore system settings can choose different routes. If location matters, look up the observed exit address and save both endpoint and exit with the result.