Elite vs Anonymous Proxy: Anonymity Levels and What They Miss
By the ProxyV4 Engineering Team · Updated:
An elite (high-anonymity) proxy hides your IP and adds no headers that reveal a proxy, an anonymous proxy hides your IP but announces itself with headers such as Via, and a transparent proxy passes your real IP along in X-Forwarded-For. These levels describe what an HTTP proxy adds to plain http:// requests. For HTTPS sites and SOCKS proxies the proxy cannot add headers at all, so what a site learns comes mostly from the IP address itself.
Elite proxy vs anonymous proxy vs transparent proxy
The three levels come from free proxy lists and proxy checkers, not from any standard. They classify a proxy by what a test server finds in the HTTP headers of a request that passed through it, and they compare two things: whether your real IP appears, and whether the request reveals that a proxy was involved.
| Level | Your IP visible to the site? | Proxy use visible in headers? | Typical headers on plain HTTP |
|---|---|---|---|
| Elite (high anonymity) | No | No | No forwarding headers added |
| Anonymous | No | Yes | Via, or X-Forwarded-For with the proxy's IP or a placeholder such as unknown |
| Distorting (a kind of anonymous) | No | Yes | X-Forwarded-For with a made-up IP |
| Transparent | Yes | Yes | X-Forwarded-For with your real IP, usually Via too |
The headers that reveal a proxy
When an HTTP proxy forwards a plain http:// request, it rebuilds the request and can add headers on the way. HTTP itself asks proxies to identify themselves: the HTTP semantics specification (RFC 9110) says a proxy should add a Via header to messages it forwards. Anonymizing proxies deliberately skip that step.
X-Forwarded-For and Forwarded
X-Forwarded-For began as a de facto header, popularized by the Squid cache, that lists the client IP and each proxy the request passed through. A request that went through one proxy for a client at 203.0.113.195 might arrive with X-Forwarded-For: 203.0.113.195. RFC 7239 standardized the same idea as Forwarded: for=203.0.113.195;proto=http;by=198.51.100.42.
Squid shows how a single setting moves a proxy between levels: its forwarded_for option can send the client IP (transparent), send unknown (anonymous), or omit the header entirely, and via off removes the Via line.
Other headers checkers look for
Some proxy software and load balancers add X-Real-IP, Client-IP or X-Proxy-ID. Proxy-Connection is a header some clients send to the proxy itself; a proxy that forwards it to the site exposes its presence. Proxy checkers flag any of these, and their presence is what moves a proxy from elite to anonymous or transparent.
Why the levels only apply to plain HTTP
This is the part most anonymity guides leave out. For an https:// URL, the client sends CONNECT host:443 to the proxy and then runs TLS through the resulting tunnel. The request headers the site receives are inside that encrypted stream, so the proxy cannot read or add to them. An HTTP proxy that is "transparent" on http:// pages adds nothing to HTTPS requests that pass through a CONNECT tunnel.
The only way a proxy can change HTTPS headers is to intercept TLS, which requires your device to trust the proxy's own certificate authority, as some corporate networks do. Without that, your client rejects the certificate.
SOCKS proxies relay bytes without understanding HTTP, so they never add Via or X-Forwarded-For. Since most of the web now runs on HTTPS, header-based anonymity levels matter mainly for plain-HTTP targets and for testing old proxies from public lists.
What sites still see behind an elite proxy
An elite label only means the headers are clean. The site still sees the proxy's IP address, and that address carries information you cannot strip: the network that owns it, its registration country, and whether IP-intelligence databases classify it as hosting, consumer broadband or mobile. Many sites decide how to treat a visitor from that data and from the visitor's behavior, not from headers.
You can see much of this yourself. Look up your proxy's exit address in the IP lookup tool to check the owning network and location a site is likely to see, and the my IP tool to confirm which address your browser is actually using.
Leaks outside the proxy
Headers are not the only way an IP slips out. In a browser, WebRTC can reveal local and public addresses to a page's scripts, and some apps resolve DNS or open connections outside the proxy settings. Run the WebRTC leak test with the proxy enabled, and use socks5h:// or an HTTP proxy so hostnames are resolved at the proxy.
Where ProxyV4 fits, and where it does not
ProxyV4 sells private IPs with one tenant per IP for the whole term. Private datacenter IPv4 is available in the United States, Vietnam, Japan, South Korea, Singapore, the United Kingdom and Hong Kong; static ISP proxies are fixed IPs registered to consumer internet providers in the United States and Vietnam. Every paid proxy supports HTTP(S), and private IPv4 outside Vietnam and US static ISP proxies also support SOCKS5 with username and password login, and you choose HTTP only, SOCKS5 only, or both on the same port on the order's page in the dashboard.
For HTTPS sites and SOCKS5 mode, the header question above does not arise. For plain HTTP, do not take any provider's anonymity label on trust, ours included: run the test in the next section on your own line before you depend on it.
Be clear about what the IP type tells a site. A datacenter IPv4 address belongs to a hosting network, and a lookup shows that; if a site only accepts consumer connections, a static ISP IP is the closer fit, and if it only accepts mobile carrier IPs, ProxyV4 does not sell those. IPv6 proxies are a separate product that only works on IPv6-ready sites, and rotating proxies are waitlist only. Prices are per IP per month; see live prices and test a single IP first. A proxy that fails for a technical reason, such as not connecting or showing the wrong location, is covered by the refund policy as a credit to your account balance.
Test your proxy's anonymity level yourself
Public header-echo services sit behind their own load balancers, which can add or hide forwarding headers and muddy the result. The cleanest test uses a tiny echo server you run on any machine with a public IP. This one returns the TCP source address it saw and every header it received:
# echo_headers.py: run on a server you control, then open http://SERVER_IP:8000/
import json
from http.server import BaseHTTPRequestHandler, HTTPServer
class Echo(BaseHTTPRequestHandler):
def do_GET(self):
body = json.dumps({
"client_ip": self.client_address[0], # the TCP source the server sees
"headers": dict(self.headers),
}, indent=2).encode()
self.send_response(200)
self.send_header("Content-Type", "application/json")
self.send_header("Content-Length", str(len(body)))
self.end_headers()
self.wfile.write(body)
HTTPServer(("0.0.0.0", 8000), Echo).serve_forever()Then request it from your own machine twice, once directly and once through the proxy, over plain HTTP so the proxy has the chance to add headers:
import requests
ECHO_URL = "http://198.51.100.20:8000/" # plain HTTP on purpose
PROXY = "http://USER:[email protected]:8080"
REVEALING = ["via", "x-forwarded-for", "forwarded", "client-ip", "x-real-ip", "x-proxy-id"]
def seen(proxies):
r = requests.get(ECHO_URL, proxies=proxies, timeout=10)
data = r.json()
return data["client_ip"], {k.lower(): v for k, v in data["headers"].items()}
direct_ip, direct = seen({"http": None})
proxy_ip, proxied = seen({"http": PROXY})
print("Server saw:", direct_ip, "directly and", proxy_ip, "through the proxy")
print("Added or changed:", {k: v for k, v in proxied.items() if direct.get(k) != v})
print("Revealing headers:", [h for h in REVEALING if h in proxied] or "none")Read the result like a proxy checker would. If the proxied request shows your real IP anywhere, the proxy is transparent. If it shows a Via or forwarding header without your IP, it is anonymous. If the only differences are the source address and no revealing headers appear, it behaves as an elite proxy for plain HTTP. For HTTPS, the headers your client sends reach the site unchanged unless TLS is being intercepted.
Frequently asked questions
Does an elite proxy hide that I am using a proxy?
It hides the headers that announce one. Sites can still look up the IP's owner and type, and many treat hosting-network addresses differently from consumer ones.
Which HTTP headers reveal a proxy?
Mainly Via, X-Forwarded-For and Forwarded, plus less common ones such as X-Real-IP, Client-IP and X-Proxy-ID. They only appear on requests the proxy can read, which means plain HTTP.
Can a transparent proxy expose my IP on HTTPS sites?
Not through headers on a normal CONNECT tunnel, because the request is encrypted end to end. It can only do so if your device trusts the proxy's certificate and it intercepts TLS.
Do SOCKS5 proxies have anonymity levels?
Not in the header sense. SOCKS5 relays bytes without parsing HTTP, so it does not add forwarding headers; the site sees the proxy's IP.
How do I check what a site sees from a ProxyV4 line?
Look up the exit IP in the IP lookup tool for its network and location, and for plain HTTP run a header echo test through the line before relying on it.
Check what a site sees from your line
ProxyV4 private IPv4 and static ISP proxies give you one IP per tenant over HTTP(S) or SOCKS5 with username and password. Order one IP and test it with your own echo server.
See live prices