Use this proxy anonymity checker to classify a proxy as elite, anonymous, transparent, or unknown by comparing its exit IP with seven common HTTP header signals.
Check proxy anonymity and headers
A proxy URI scheme overrides the dropdown. Your browser IP is compared only on this page and is never sent to the anonymity API.
What This HTTP Proxy Header Test Measures
MiyaIP obtains a direct-request baseline, sends a request through the proxy to the same fixed HTTP target, and compares the target's observed exit address with seven common forwarding and proxy-header signals. The result answers whether this request exposed the test-node source address or recognizable proxy traces.
The proxy request begins at the MiyaIP test node, so that node is the source a proxy could expose. Your browser's public IP is used only for a local exit comparison and is never sent in the proxy anonymity request.
How This Proxy Anonymity Test Classifies Each Proxy
Elite means the source address was hidden and none of the seven known proxy-added headers was observed. Anonymous means the source was hidden but headers such as Via or Forwarded revealed proxy use. Transparent means the source was not replaced or a forwarding header contained it.
Unknown is used when the proxy is unavailable, evidence is incomplete, or a reliable direct baseline cannot be obtained. Each of the seven header checks remains visible so the classification can be reviewed without exposing raw header values.
Anonymity evidence is not a security guarantee
This server-side test does not detect browser WebRTC, client DNS routing, browser fingerprinting, account association, operator logging, malicious content, or long-term stability. Use the browser environment check for browser-side IPv4, IPv6, DNS, and WebRTC signals.
Credentials are used only for the active backend connection, and copies, exports, results, URLs, and history are redacted. Retest after changing the endpoint or protocol, and never send sensitive traffic through a proxy you do not trust regardless of its rating.
Elite, Anonymous, Transparent, and Unknown
The classification is derived from the fixed HTTP request made by the MiyaIP node through the proxy. It describes observable source-address and header behavior for that request, not the proxy operator’s policies or every application protocol.
Proxy anonymity levels
Level
Source address
Known proxy headers
Interpretation
Elite
The test-node source was not observed as the exit or inside the checked headers.
None of the seven checked proxy-added headers was observed.
The request hid the tested source and did not leave these common HTTP proxy traces.
Anonymous
The test-node source was hidden.
At least one checked header signalled proxy use without exposing the source.
The origin was hidden, but the target could recognize proxy behavior.
Transparent
The exit matched the source or a checked forwarding header contained the source.
May include forwarding or proxy identifiers.
The request did not hide the test-node source from the target.
Unknown
Could not be established reliably.
Evidence was incomplete or the request/baseline failed.
No anonymity conclusion should be inferred; troubleshoot and retest.
Seven HTTP Headers Checked by the Test
Header names are case-insensitive. MiyaIP reports whether each known signal was observed and whether relevant forwarding evidence contains the test-node source, while avoiding display of raw values that could expose internal identifiers.
Forwarded
The standardized forwarding header can describe the originating client, proxy, host, and protocol. A for parameter containing the source is strong transparency evidence.
X-Forwarded-For
A widely used non-standard chain of client and proxy addresses. Its ordering and trust depend on the infrastructure that writes it.
X-Real-IP
Often carries a single client address selected by a reverse proxy. It is conventional rather than a universal standard.
Client-IP
A legacy or implementation-specific client-address header. Its presence is a proxy trace, and a source match can indicate exposure.
Via
Identifies intermediary protocol hops. It can reveal proxy use without necessarily containing the originating address.
Proxy-Connection
A non-standard hop-control header used by some proxy implementations and clients. Its presence is a recognizable proxy signal.
X-Proxy-ID
An implementation-specific identifier sometimes added by proxy infrastructure. It can reveal an intermediary even when the source remains hidden.
Source IP, Exit IP, and Header IP Example
Suppose the MiyaIP test node uses 198.51.100.x, the target sees proxy exit 203.0.113.x, and X-Forwarded-For also contains 198.51.100.x. The addresses are documentation-only and masked here. Although the exit changed, the header repeats the source, so the request is transparent under this test.
If the target sees 203.0.113.x, the source does not appear, but Via is present, the result is anonymous: the source is hidden while proxy use is visible. If no checked header appears and the exit differs from the source, the observed request can be elite. Every conclusion remains scoped to this node, target, protocol, and time.
Illustrative header evidence
test-node source: 198.51.100.x
proxy exit: 203.0.113.x
X-Forwarded-For: contains 198.51.100.x
classification: Transparent for this request
HTTP and SOCKS Anonymity Testing Differences
The fixed target uses HTTP because an HTTP intermediary may add Forwarded, Via, or related headers that the echo service can observe. With an HTTPS tunnel, application request headers are encrypted between the client side of the tunnel and the destination, so an intermediary cannot normally insert the same visible HTTP fields without terminating TLS.
SOCKS forwards connections below HTTP and does not define these HTTP headers. A SOCKS endpoint can therefore look elite in this header-focused test while still logging traffic, revealing other protocol metadata, or routing DNS differently in a real client. The test remains useful for comparing exit and source behavior, but the absence of HTTP headers has less diagnostic depth for SOCKS.
Anonymity, Privacy, and Security Are Different
Anonymity here means whether the fixed target can link the request to the MiyaIP test-node source through the exit or seven headers. Privacy also depends on DNS, WebRTC, browser fingerprinting, accounts, cookies, destinations, provider logging, and traffic correlation. Security additionally requires trustworthy software, endpoint authentication, encryption, patching, and protection against malicious responses.
Unknown is deliberately inconclusive. It can result from an unavailable proxy, failed fixed target, missing baseline, or incomplete evidence and must not be treated as either safe or transparent. Even an Elite result says nothing about malware, credential theft, content injection, legal jurisdiction, retention policy, or future behavior. Use replaceable credentials and avoid sensitive traffic through untrusted infrastructure.
FAQ
Frequently asked questions
How does the proxy anonymity checker determine the result?
MiyaIP compares a direct-request baseline with a request through the proxy to the same fixed HTTP target. It checks the exit IP and seven known headers, then reports elite, anonymous, transparent, or unknown from the available evidence.
What does an elite proxy result mean?
Elite means this request hid the test-node source IP and the target did not observe any of the seven known proxy-added headers. It does not evaluate the operator, encryption, logging policy, malicious content, or account security.
Why does the test use the MiyaIP server IP instead of my public IP?
The proxy request starts from the MiyaIP test node, so that node is the source a proxy could expose. Your browser public IP is used only for a local exit comparison and is not the source of the server-side request.
Why does the HTTP proxy header test use a fixed HTTP request?
HTTPS request headers are inside an encrypted tunnel and cannot normally reveal headers added by an HTTP proxy. A fixed HTTP echo target exposes Forwarded, Via, and related evidence without carrying your browsing data or accepting a custom destination.
Can this proxy anonymity test detect WebRTC, DNS, or browser fingerprint leaks?
No. It measures the test-node source address, proxy exit, and seven HTTP headers. Use the browser environment tool for browser-side IPv4, IPv6, DNS, and WebRTC signals.
Why are raw HTTP header values not displayed?
The classification needs only whether the proxy added a header and whether it contains the test-node source address. Hiding raw values reduces exposure of proxy identifiers and internal information while preserving a reviewable status for every check.
Are proxy credentials saved?
No. Credentials are used only for the current backend connection and do not appear in responses, copied summaries, exports, the address bar, browser history, or saved results.
Is an Elite proxy completely anonymous?
No. Elite only means this test did not observe the node source or seven known proxy headers. Accounts, cookies, browser fingerprints, DNS, operator logs, traffic correlation, and other protocols can still identify or link activity.
Why does Via make a proxy Anonymous instead of Transparent?
Via can reveal that an intermediary exists without revealing the originating source address. Transparent requires source exposure through the exit or checked forwarding evidence.
What should I do with an Unknown result?
Check connectivity, credentials, protocol, and the reported baseline or target error, then retest. Unknown means evidence was insufficient and should never be interpreted as a pass.
