Proxy tools
IP address checker
See the public IP address the server sees for your connection, whether it is IPv4 or IPv6, and which proxy-related headers your request carries.
Your public IP address
…
How it works
What this tool does
You send a request
Your browser asks our server for the connection details of this very request.
We read the real values
The address comes from the network connection and forwarded headers, not from a guess or third-party database.
We classify it
The address is labelled public, private, loopback, CGNAT and so on.
How to read the result
Run the check once without a proxy and once with it enabled. If the address changes to the proxy’s exit IP, your traffic is routed correctly.
Proxy-related headers such as Via or X-Forwarded-For reveal that a proxy sits in the path. Elite proxies send none, while transparent proxies send your real IP; this tool shows what actually arrived.
In depth
The details that decide the outcome
How the server decides which address is yours
A web server can only see the source address of the TCP connection that reached it, which is the last hop, not necessarily you. When a site sits behind a CDN or reverse proxy, the original client address is passed along in headers instead. This tool reads CF-Connecting-IP first, then the first entry of X-Forwarded-For, then X-Real-IP, and falls back to 127.0.0.1 when none exist, as on a local development machine. These headers are trustworthy only when set by infrastructure in front of the server, because any client can send a forged one.
The result is classified by range. Private space (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) is never routed on the public internet, so seeing it means a local or misconfigured path. Carrier-grade NAT space (100.64.0.0/10) is shared by many subscribers of one operator. Loopback and link-local addresses never leave your machine or network segment. The version field matters too: a dual-stack browser chooses IPv6 or IPv4 per connection, so two visits can legitimately show different versions, and a proxy that offers only IPv4 will always show an IPv4 exit.
Worked reading: a before-and-after run with a proxy
Run the tool twice and compare. Illustrative example with placeholder values: without a proxy you see address A (IPv6, class public) and no proxy headers. With the proxy enabled you see address B (IPv4, public) and one header, Via. That is the expected pattern: the exit changed, so this request left through the proxy. If address A still appears, the request bypassed the proxy, which usually means the application ignores the system proxy setting, a per-domain rule excludes this site, or the extension is off.
Read the headers with care. A listed Via, Forwarded or X-Forwarded-For header shows that a hop added it, but not which hop: the hosting layer in front of this site can add its own, so judge the difference between your two runs rather than a single run. If your original address appears inside X-Forwarded-For on the proxied run, that proxy is passing your address on. The tool inspects one request only. It does not test WebRTC, DNS leaks or browser fingerprints, so treat a clean result as a first check, not proof of anonymity.
| What you see | Likely meaning | Next step |
|---|---|---|
| Same address with and without the proxy | Traffic bypassed the proxy | Check proxy settings, per-domain rules and extensions, then repeat. |
| Different address, no proxy headers | The exit changed and the proxy does not announce itself | Confirm the exit with the proxy checker and look it up in IP information. |
| Different address, your original address inside X-Forwarded-For | The proxy forwards your address | Check the proxy’s anonymity setting or ask sales. |
| Class shows private or CGNAT | The server saw a non-public or shared source | Repeat on the live site over the public internet, not a local setup. |
FAQ
Tool questions
Why does it show a local address?
On a development machine the request never leaves your computer. Deployed behind a reverse proxy, the real client address is read from the forwarded headers.
Is this check stored?
No lookup history is stored.
Does it show my location?
No. For registry details of an address, use the IP information tool.
Why can the tool show a different version on different visits?
Dual-stack networks offer both IPv4 and IPv6, and a browser may choose either for each connection, so the version shown describes that single request. Run the check a few times, and compare it with the version your proxy uses, before drawing conclusions.
Does the tool show whether my proxy leaks my real address?
Only in part. It shows the address and forwarding headers of one HTTP request. It cannot see WebRTC candidates, DNS queries or traffic from other applications, so a clean result does not rule out those leaks.
Not sure which plan fits?
Describe your use case and target countries and we will recommend a product — or tell you honestly when another type suits you better.