VPN and proxy IP check
Compare the public IP reaching this server with the exit expected from a VPN, browser proxy, or company gateway.
- Address family
- IPv4
- Network
- Loading network context…
- Approximate area
- Loading location estimate…
- Reverse name
- Loading reverse name…
Quick answer
This comparison reports the public address and network reaching the server. Save a direct baseline, enable the VPN or proxy, and repeat in the same browser. A change to the expected operator supports that this request used the configured exit; it does not certify every application or connection path.
Compare a VPN, proxy, or gateway exit with a saved baseline
Use this page after recording the homepage result without the intermediary. Enable the intended tunnel, browser proxy, or managed gateway, repeat under the same conditions, and compare the visible address with the exit you selected. That confirms this web request’s route, not every application or protocol on the device.
Verify an expected VPN exit
Check that the provider and broad region fit the chosen endpoint while treating city placement as an approximate database label.
Confirm a configured proxy
Repeat in the application that actually uses the proxy; another program can follow the direct route and produce a different valid result.
Investigate an unchanged address
Confirm client state, proxy scope, split-tunnel rules, address-family support, and failure behavior before assigning a cause.
Follow the result into the next relevant page
Read VPN trust-boundary guide because it explains what changes and what remains visible; Read full IP lookup because it adds network and approximate-area context to an exit; Read browser fingerprint report because it covers signals a changed IP does not erase.
How to interpret the output
A device-wide VPN normally changes the exit for routed applications. A browser proxy or company gateway may handle only selected software or protocols, so two applications can legitimately show different public addresses. Provider and hosting labels are contextual clues, not deterministic proof that a proxy exists.
A reliable checking workflow
Record the homepage result before changing settings. Enable the VPN, browser proxy, operating-system proxy, or managed gateway, then repeat here. Compare the address and network with the configuration you control. If another application differs, inspect its proxy and split-tunnel rules rather than calling the first result a leak.
Key ideas behind vpn and proxy ip check
A VPN or proxy check is a controlled before-and-after comparison. It can confirm the public exit used for this page, but it cannot inspect every application or promise anonymity.
Baseline
The direct address and provider show what reached the server before the tunnel was enabled.
Expected exit
A changed address in the chosen VPN network supports the claim that this browser request used the tunnel.
Application scope
A browser proxy may cover this page while another program uses the direct route; VPN split-tunnel rules can create the same difference.
Example: the browser changes exit while another app does not
You enable a browser proxy and this page shows the expected exit provider, while a chat app continues to show the ISP route. Both can be correct because the proxy is application-specific. A device-wide VPN may behave differently, and accounts or cookies can still link activity above the network layer.
The boundary that matters
A browser-only check cannot inspect VPN encryption, verify a no-logs claim, detect a transparent intermediary, or observe software outside this request. An unchanged address is a reason to inspect settings; a changed address confirms one route but does not establish anonymity or system-wide coverage.
VPNs and proxies are not interchangeable. A VPN usually creates an encrypted network tunnel to an exit server. An HTTP or SOCKS proxy relays configured application traffic and may not protect traffic between the device and proxy. A corporate secure web gateway can combine proxying, filtering, and authentication. The useful test is whether the visible exit matches the specific route you intentionally configured.
How the main entities relate
| Subject | Relationship | Object |
|---|---|---|
| Configured intermediary | changes | the public exit for routed traffic |
| Application proxy | can cover | only selected software |
| User account | can still link | activity above the network layer |