Proxy anonymity level — transparent, anonymous, or elite (high-anonymity) — describes what an HTTP proxy reveals about itself through request headers, independent of the IP-type tiers covered elsewhere in this glossary (residential, datacenter, mobile, ISP): it's a question of header behavior, not of where the IP address comes from.
Transparent forwards the request without hiding anything, typically adding both an X-Forwarded-For header carrying the client's real IP and a Via header announcing a proxy is in use — a destination can see both that a proxy sits in front of the request and exactly which IP it's hiding. These are mostly used for caching or filtering inside a network, not for anonymity. Anonymous still identifies itself as a proxy, usually via a Via-style header, but doesn't leak the client's real IP — a destination knows a proxy is involved but can't directly read who's behind it.
Elite, also called high-anonymity, strips every proxy-identifying header, so a request looks indistinguishable at the HTTP-header layer from one sent with no proxy at all — no Via, no X-Forwarded-For, nothing announcing the proxy's presence. This is the tier virtually every commercial scraping proxy markets by default, because it's the baseline a scraper needs before IP type and rotation even start to matter.
IP-type tiers answer "whose network does this IP belong to," which drives a target's trust and reputation scoring of the address itself. Anonymity level answers a different question — "does the HTTP request carry any header revealing a proxy is involved" — and the two combine independently: a residential IP routed through a misconfigured transparent proxy still leaks the real client IP in a header, while an elite-anonymity datacenter proxy hides the proxy's presence but is still recognizable as a datacenter IP by its ASN.
Being elite-anonymity is table stakes for commercial proxy providers today, not a differentiator — nearly every paid residential or datacenter proxy pool runs elite-tier by default, since a header-leaking proxy wouldn't be commercially viable for scraping at all. What actually separates proxy providers in 2026 is IP-type trust and rotation quality, not whether headers leak.
import requests
proxies = {
"http": "http://user:pass@proxy.example.com:8000",
"https": "http://user:pass@proxy.example.com:8000",
}
response = requests.get("https://httpbin.org/headers", proxies=proxies, timeout=15)
print(response.json()["headers"])
# Elite/high-anonymity: no Via or X-Forwarded-For key present
# Anonymous: Via present, no X-Forwarded-For
# Transparent: both present, X-Forwarded-For carries your real IPHow Crawlora handles this
Crawlora's proxy layer runs elite-anonymity by default across every IP type it offers, so no proxy-identifying header ever reaches the target — anonymity level isn't a tier you pick, it's the floor every request starts from, leaving IP type and rotation as the actual levers you configure.
Glossary
FAQ
No — elite/high-anonymity describes header behavior (no proxy-identifying headers leak), while residential describes IP source (an ISP-assigned home connection). A proxy can be elite-anonymity and still be a datacenter IP, or residential and still leak headers if misconfigured.
Rarely as a differentiator — nearly every commercial proxy provider runs elite-anonymity by default today, since a header-leaking proxy isn't commercially viable for scraping. IP type and rotation quality matter far more for avoiding blocks.
Send a request through it to an endpoint that echoes headers back, like httpbin.org/headers, and check for a Via or X-Forwarded-For key in the response — their presence, and whether X-Forwarded-For carries your real IP, tells you the tier.
Beyond Proxy Anonymity Levels, Crawlora's own docs cover the rest of the stack — browse the APIs, test a request in Playground, and move from scraping infrastructure work to production data workflows.