More unique IPs than any network on the planet, in the world's largest residential pool. That's Shifter.More unique IPs than any network, in the world's largest pool. That's Shifter.

See the numbers

Proxy Anonymity Levels: How to Check a Provider's Proxies Don't Leak Your IP

What transparent, anonymous and elite proxies are, why the labels say little about residential proxies, and the five leak checks that actually show whether a proxy gives away your IP or location.

Chris Collins Engineering · Updated November 6, 2026 · 6 min read
yousiteDNSWebRTCheaders
A proxied request. Amber leaks give your real IP away.
Authenticity
On this page
  1. The three anonymity levels
  2. Why the levels say little about residential proxies
  3. The leaks that matter
  4. How Atlas checks for leaks
  5. Checking your own setup
  6. What anonymity levels cannot tell you
  7. Frequently asked questions

Proxy lists, and some providers, still label proxies by anonymity level: transparent, anonymous or elite. The labels come from the era of public open proxies, and they answer a narrow question: what does the proxy tell the website about you in its HTTP headers? If you use residential proxies for data collection or testing, that question still matters, but it is only one of several ways your own IP or location can leak.

This guide explains the three levels, why nearly every commercial residential proxy is “elite” by that definition, and the checks that actually tell you whether a proxy leaks. One honest caveat first: a proxy changes the address a site sees. It is not an anonymity tool, and what a proxy does not hide is worth reading before you rely on one for privacy.

The three anonymity levels

The classic classification looks only at request headers:

  • Transparent. The proxy forwards your real IP, usually in an X-Forwarded-For header, and announces itself with Via. The site knows that you are using a proxy and who you are.
  • Anonymous. The proxy hides your IP but still announces itself, through Via, Proxy-Connection or similar headers. The site knows a proxy is in use, but not your address.
  • Elite (high anonymity). The proxy adds no identifying headers. From the headers alone, the request looks as if it came directly from the exit IP.

Checking the level is easy: send a request through the proxy to an endpoint that echoes headers back, and look for Via, X-Forwarded-For, Forwarded, X-Real-IP and Proxy-Connection.

Why the levels say little about residential proxies

Any reputable residential proxy service should be elite. Adding your IP to the headers would defeat the product, and announcing the proxy would get every request flagged. If a provider is not elite, that is a disqualifying finding, and you will see it in the first test.

The bigger issue is that headers are no longer the main way a connection gives itself away. Since anonymity levels were defined, sites have learned to read the TLS handshake, the DNS path, browser APIs and IPv6 routes. A proxy can be perfectly elite and still let your real location out through any of them. Some of those leaks are the provider’s responsibility, and some are your client’s.

So “elite” is a floor. It tells you the proxy is not actively telling on you. It does not tell you that nothing else is.

The leaks that matter

These are the five channels worth checking on any proxy you use for real work:

  • Proxy headers. The anonymity-level check above. The provider controls this one.
  • DNS. If hostnames are resolved on your machine rather than through the proxy, the lookup goes to your own resolver, and a site that can see resolver traffic learns your country. With SOCKS5, this is the difference between socks5 and socks5h in many clients. The guide to preventing DNS leaks covers the fix for each common client.
  • WebRTC. In a browser, WebRTC can expose local and public addresses to the page, bypassing the proxy entirely. This is a client setting, but it matters whenever you drive a real browser through a proxy.
  • IPv6 fallback. If your machine has IPv6 and the proxy only tunnels IPv4, some traffic may go out directly on your own address.
  • TLS fingerprint. Not a leak of your IP, but a leak of what you are. A handshake that matches a client library rather than a browser marks the request as automated, which is often enough to get it challenged. It sits next to browser fingerprinting in most detection stacks.

How Atlas checks for leaks

Atlas runs these five checks on every network it tests, and asserts them from the target side: what the site actually received, not what the client was configured to send. A network passes when the resolver seen by the target matches the exit country, no local addresses reach the page, no proxy headers arrive, the handshake matches a mainstream browser build, and no unproxied IPv6 route is preferred over the tunnel.

The definitions are in the Atlas metrics, and the side-by-side network comparison shows how many checks each network passes. Every network runs the same checks with the same client, Shifter included, so a failure points at the network rather than at a difference in configuration.

Two limits are worth stating. A passed check means the network did not leak with Atlas’s client; your own client can still leak on its own. And the leak checks are shown next to the Atlas Score, not counted in it.

Checking your own setup

Most leaks in practice come from the client, so test the setup you will actually run, not just the proxy:

  1. Headers. Request a header-echo endpoint through the proxy. Nothing should name a proxy or contain your own IP.
  2. IP and country. Confirm the echoed IP is the exit, and that it geolocates where you asked.
  3. DNS. Use a DNS leak test through the proxy. The resolver should be in the exit country, not yours. If you use SOCKS5, make sure the client resolves hostnames remotely.
  4. WebRTC. If you drive a browser, open a WebRTC leak test page through the proxy. No address except the exit should appear. Disable or restrict WebRTC if one does.
  5. IPv6. Visit an IPv6 test page through the proxy. If it reports your own IPv6 address, disable IPv6 on that machine or route it through the tunnel.
  6. Fingerprint. If targets challenge you on clean exits, compare your TLS handshake with a real browser’s.

Run these once per client, and again whenever you change libraries, browser versions or machines.

What anonymity levels cannot tell you

Even a proxy that passes every check does not make you anonymous. The provider sees your traffic metadata, your account ties requests to you, and anything you send inside the request, such as cookies or logins, identifies you whatever the IP. Anonymity levels and leak checks confirm that the proxy does what it says: present the exit address and nothing else. For data collection, that is what you need. For privacy, it is only the start.

Frequently asked questions

What are proxy anonymity levels?

They describe what a proxy reveals in its HTTP headers. A transparent proxy forwards your real IP, an anonymous proxy hides your IP but announces itself, and an elite proxy adds no identifying headers.

Are residential proxies elite proxies?

Any reputable residential proxy service should be elite, because adding your IP to the headers would defeat the product. If a provider is not elite, that is a disqualifying finding, and it shows in the first test.

Can an elite proxy still leak my IP or location?

Yes. Elite only covers headers. DNS lookups, WebRTC in a browser and IPv6 fallback can still expose your IP or location, and a TLS handshake can mark the request as automated. Many of these leaks come from the client, not the provider.

How do I check whether my proxy leaks?

Request a header-echo endpoint through the proxy, then confirm the exit IP and its country. Next run DNS, WebRTC and IPv6 leak tests from the setup you will really use, and again whenever you change libraries, browsers or machines.

Does a proxy make me anonymous?

No. A proxy changes the address a site sees. The provider still sees your traffic metadata, your account ties requests to you, and cookies or logins inside a request identify you whatever the IP.

Get started

Check for leaks with your own client

Start a free trial on Shifter's residential network and run the header, DNS, WebRTC and IPv6 checks from the setup you will use in production.

3-day money-back guarantee. Cancel anytime.