IP Lookup & Connection Check

How to Interpret These Results

Public IP: The address websites see

This is usually the public address of your current network or selected route, not your device’s local network address. Checking before and after connecting can help confirm whether your browser traffic has switched routes. With split tunneling, different websites may use different routes, so these results don’t represent every connection.

Location: An estimate from an IP address database

The location is based on an IP address database, not your device’s location. IP allocations, data center moves, and database updates can all affect accuracy. If the displayed region doesn’t match your selected route, check again, then compare the client’s route name with the target website’s behavior.

ISP: The network organization associated with your public IP

This may show the name of an internet provider, data center, or hosting network—not necessarily VPNCross. The organization name and public IP can help identify the network source, but the name alone doesn’t indicate speed, connection quality, or access permissions.

Proxy detection: An indicator, not a security verdict

Results depend on the API’s data and detection methods, which may be outdated or inaccurate. “No proxy detected” doesn’t mean you aren’t using one, and “Proxy detected” doesn’t mean anything is wrong. If the API can’t make a clear determination, this page will show “Temporarily unavailable.”

How to Check for DNS Leaks

DNS translates domain names into network addresses. A change in your public IP doesn’t mean DNS requests are using the same route. This page’s GeoIP lookup doesn’t retrieve a list of DNS resolvers, so it can’t determine on its own whether a DNS leak has occurred.

1. Check your client first. Make sure the route is connected. Check whether you’re using global mode or split tunneling, and whether DNS requests are being handled by the client as expected. Depending on your settings, some requests may intentionally use your local network.
2. Then check your browser. Review your “Secure DNS” or encrypted DNS settings. A DNS service set directly in your browser may differ from your system or client configuration, so check each setting. This page’s IP result alone isn’t enough to tell.
3. Compare resolver results. If you use a dedicated DNS test, review its privacy policy first. Then compare the resolver’s network and organization before and after connecting with your expected routing rules. With distributed DNS services, the resolver’s location may differ from your public IP’s location.
4. Test again after making changes. After changing DNS or split-tunneling settings, reconnect to the route and reopen your browser to test. If you still have questions, describe your mode, route, and the issue in a support ticket through the user panel.

Query Privacy & Error Messages

We don’t log queries. Lookups use an API on this site; the page doesn’t call third-party public IP lookup services or save results in your browser’s local storage. Copying happens only when you click the button.

If the API is unavailable, a request times out, or a field is missing, the relevant result will show “Temporarily unavailable”—never a sample address. Check your connection and click “Check Again.” A failed lookup doesn’t tell you whether your route is connected.

Before sharing a screenshot or submitting a support ticket, consider hiding your full IP address. Don’t include passwords or subscription links. For details about how we handle data, see our Privacy Policy.