Network Check · Current Browser Connection
IP Lookup
See where this browser request connects to the internet. Check again after switching routes to compare the results.
Current Connection Details
VPNXM Lookup ServiceUnable to retrieve results right now. Enable JavaScript for automatic lookup, or run the check again manually.
- Public IP Address
Unable to retrieve- Location
- Unable to retrieve
- ISP / Network Provider
- Unable to retrieve
- Proxy Detected
- Unable to retrieve
Location and proxy status are based on the service response and are for troubleshooting only. This card does not check for DNS leaks or represent the network path used by every app.
Understanding the Results
Public IP: The address websites see
The public IP is the network address seen by VPNXM’s lookup service. It is usually different from your device’s address on a local network. After connecting a client, your public IP will typically change if browser traffic uses the selected route. Whether it does depends on the client mode, routing rules, and browser settings—not just the client’s connection indicator.
Location and ISP: Results from IP databases
A location is an IP database’s estimate, not your device’s precise location. The ISP field may show a network provider, data center, or organization associated with the address. Databases vary in how often they’re updated, so the same IP can be labeled differently across websites. If locations don’t match, consider the results alongside your actual access experience.
Proxy Detection: A Clue, Not a Security Verdict
“Proxy detected” means the lookup service classified the connection’s public IP as proxy-related. “No proxy detected” only means no such flag was found this time; it doesn’t mean you aren’t using a VPN. If the service can’t make a definite determination, this page shows “Unable to retrieve” rather than treating missing data as a negative result.
Compare before and after connecting: Check your public IP before connecting, then connect to your chosen route and click “Check Again.” If the IP hasn’t changed, check whether your browser uses the proxy, whether the request matches your routing rules, and whether other proxy settings are active. For more troubleshooting, see the Guides or FAQs.
DNS Leak Check
DNS translates domain names into network addresses. A changed public IP doesn’t prove that DNS requests use the same route. This page only checks the public IP of a web request; it doesn’t send a dedicated DNS query to a test domain, so it can’t determine whether a DNS leak has occurred.
- Review your client settings. Make sure your DNS, routing rules, and tunnel mode are configured as intended. Settings vary by platform, so refer to the documentation for your client.
- Check your browser settings. Secure DNS or custom DNS settings in your browser may use a separate route. Review how they’re configured before making changes; there’s no need to disable existing protections just to run a check.
- Use a dedicated test that shows the resolvers. To investigate further, choose a tool you trust and compare the resolver details and expected route before and after connecting. The tool will receive the related test requests, so review its privacy policy before using it.
- Interpret results in context. A resolver’s location doesn’t have to match your public IP’s location. Public DNS services may use distributed networks. A location difference alone isn’t enough to establish a leak; check whether the resolver matches your configuration.
If DNS queries still appear to use your original network, first check your system DNS, which traffic your client routes, and any browser-specific settings, then test again. A public IP lookup alone is not a complete privacy check.
Privacy Note
VPNXM does not log lookup queries. This page requests check results only from VPNXM’s own service; it doesn’t use a third-party public API as a fallback. If a lookup fails, the page says so rather than generating a substitute result.
The copy button copies only the retrieved public IP, not the full check results. An IP address may reveal clues about your network, so consider masking it before sharing a screenshot. See the Privacy Policy for details.