To check proxy anonymity, you look at what the website actually receives: the IP address the request came from and the HTTP headers attached to it. Some proxies add headers such as X-Forwarded-For or Via that reveal your real IP or announce that a proxy is in use. Others pass requests through cleanly. Providers label proxies "transparent", "anonymous" or "elite", but a two-minute test tells you what's really happening, and it's worth running on any proxy you rely on, including ours.
The Three Anonymity Levels
- Transparent: the proxy forwards your real IP in a header like X-Forwarded-For. The site knows who you are and that you used a proxy.
- Anonymous: your real IP is hidden, but headers like Via or Proxy-Connection reveal that a proxy is in use.
- Elite (high anonymity): no extra headers. The request looks like it came directly from the proxy's IP.
These levels are explained in more depth in transparent, anonymous and elite proxies. This post is about testing.
Headers That Give a Proxy Away
- X-Forwarded-For: commonly carries the original client IP. The most important one to check.
- Forwarded: the standardized version (RFC 7239), may include for= with your IP.
- X-Real-IP and Client-IP: alternative headers some proxies use for the client address.
- Via: names the proxy hop and protocol version.
- Proxy-Connection: a non-standard header some clients and proxies leak through.
- X-Proxy-ID and similar vendor headers.
Test 1: Over Plain HTTP
Over plain http://, the proxy handles the request itself and could add headers. That's where leaks happen. Use an echo service that shows request headers:
# Your real IP, for comparison
curl -s https://api.ipify.org; echo
# What the site sees over plain HTTP through the proxy
curl -s -x http://USERNAME:[email protected]:8080 http://httpbin.org/headers
curl -s -x http://USERNAME:[email protected]:8080 http://httpbin.org/ipLook for your real IP anywhere in the output, and for any of the headers listed above. The "origin" field from /ip should show only the proxy's exit IP. If it lists two addresses separated by a comma, the second hop added a forwarding header with another address.
Test 2: Over HTTPS
Over https://, your client opens a CONNECT tunnel and does TLS directly with the site. The proxy only relays encrypted bytes and cannot add or change headers. So for HTTPS traffic, a standard CONNECT proxy is header-clean by design:
curl -s -x http://USERNAME:[email protected]:8080 https://httpbin.org/headersAny proxy-related header you see here was added by your own client, by the website's own CDN, or by something on your machine, not by the proxy. Since almost all sites use HTTPS today, header leaks from the proxy itself are mainly a concern for plain-HTTP targets.
An Automated Check in Python
import requests
PROXY = "http://USERNAME:[email protected]:8080"
proxies = {"http": PROXY, "https": PROXY}
LEAKY = ["x-forwarded-for", "forwarded", "x-real-ip", "client-ip",
"via", "proxy-connection", "x-proxy-id"]
real_ip = requests.get("https://api.ipify.org", timeout=15).text.strip()
for scheme in ("http", "https"):
data = requests.get(f"{scheme}://httpbin.org/anything",
proxies=proxies, timeout=30).json()
headers = {k.lower(): v for k, v in data["headers"].items()}
found = {h: headers[h] for h in LEAKY if h in headers}
leaked_ip = real_ip in str(data)
if leaked_ip:
level = "transparent (real IP visible)"
elif found:
level = "anonymous (proxy headers present)"
else:
level = "elite (no proxy headers)"
print(f"{scheme}: origin={data['origin']} -> {level}")
for h, v in found.items():
print(f" {h}: {v}")Run it a few times. With rotating proxies, each run uses a different exit, so you're checking the gateway's behavior across several IPs, not just one.
Leaks Headers Can't Show
Clean headers don't guarantee anonymity in a browser. Check these too:
- WebRTC can expose your real public IP to page scripts. Test in the same browser you use with the proxy.
- DNS lookups done locally (socks5:// instead of socks5h://, or misconfigured system DNS) reveal to your DNS provider which sites you visit. See DNS leaks and proxies.
- Cookies and logged-in sessions from earlier direct visits link you across IPs.
- Browser fingerprint: a consistent fingerprint ties visits together regardless of IP. See what is browser fingerprinting.
- Time zone and language that don't match the exit country.
Testing NodeProxies
Run the tests above against global.nodeproxies.xyz:8080 with your own credentials and judge the results yourself. Our what is my IP tool is a quick visual check, and how to test if a proxy is working covers speed and location checks. Plans start at $3 with no KYC; see the pricing page.
FAQ
How can I tell if my proxy is anonymous?
Request an echo service such as httpbin.org/headers over plain HTTP through the proxy. If your real IP or headers like X-Forwarded-For or Via appear, it isn't fully anonymous.
Can an HTTPS proxy add X-Forwarded-For?
Not to HTTPS traffic through a CONNECT tunnel, because the headers are encrypted end to end. It can only add headers to plain HTTP requests, unless it intercepts TLS with its own certificate.
What is an elite proxy?
One that adds no identifying headers, so the website sees a request that appears to come straight from the proxy's IP with no sign of forwarding.
Is a clean header test enough for anonymity?
No. Browsers can leak through WebRTC, DNS, cookies and fingerprinting. Check those separately.
