Browser Egress Check for VP·NOC

IP Lookup and Egress Check

See where this web request reaches VPNOC from. Check before and after connecting a route, then compare the results with how your apps behave to see whether your rules are working.

VPNOC / NETWORK CHECK

Current connection details

Applies to this request only
Public IP address
Temporarily unavailable
Country / Region
Temporarily unavailable
Internet service provider / ISP
Temporarily unavailable
Proxy detected
Temporarily unavailable

No results yet. Enable JavaScript to run the check automatically, or select Check again.

What this information means

Location and proxy detection are useful clues, but neither independently proves that your connection is working or your privacy is protected.

Public IP: the source of this request

This is the source address seen by VPNOC’s interface. Keep the result from before connecting, then check again afterward. If your browser traffic goes through the selected route, its public IP will usually change. With split routing, this page may use a direct connection, so an unchanged address doesn’t mean the route isn’t working for your other apps.

Location and ISP: clues from IP records

Country and region are generally estimated using IP databases and may differ from the device’s actual location. The ISP field may show an internet provider, hosting company, or organization associated with the egress network; it may not match the route name. Location data can be outdated, so don’t use it to infer a precise location.

Proxy detection: based on the interface’s result

A detection result appears only when the interface returns a clear assessment. Results may be affected by database updates, shared IPs, and network topology. “No proxy detected” doesn’t mean you aren’t using a route, and “Proxy detected” doesn’t mean the connection is faulty. If no assessment is returned, the page shows “Temporarily unavailable.”

Check your apps separately from your browser

This page only shows the path taken by requests to VPNOC. AI tools, streaming services, and other apps may match different rules or use their own proxy settings. Check your client’s rule-match logs alongside the results in the app you’re testing. For setup instructions, see Guides.

How to check for DNS leaks

DNS translates domain names into IP addresses. An IP lookup doesn’t run a dedicated DNS leak test, and this page doesn’t collect resolver results. The location or proxy status above can’t replace a DNS check.

  1. Confirm the expected route. Check whether your client is using global mode or rule-based routing, and whether the domain should be resolved locally or by the remote route. In rule-based mode, resolving some domains locally may be intentional.
  2. Review your DNS settings. Check DNS forwarding, remote resolution, and routing rules in your client, then review your browser’s Secure DNS settings. A browser’s built-in resolver may work differently from your client’s, so check the documentation for the software you use.
  3. Check the actual requests. After connecting to a route, open the app or website you want to test. Check the destination used to resolve the domain in your client’s connection logs or DNS diagnostics. If your client doesn’t provide this information, don’t assume the DNS path is correct just because the page loads.
  4. Test again under the same conditions. After changing settings, make another request and, if needed, clear the app’s DNS cache. Compare the observed resolution path with your expected rules. Investigate further only if a lookup that should use the route unexpectedly goes through your local resolver.
A difference between the egress location and resolver location doesn’t necessarily indicate a leak. First confirm your split-routing setup, then check whether actual DNS requests follow the rules.

To distinguish between protocol, route, and split-routing issues, see the Protocol Reference. For common connection issues, see the FAQ.

Lookup privacy and data handling

VPNOC does not log lookups. The check sends requests only to VPNOC’s interface and does not fall back to public third-party lookup services. Results aren’t saved in persistent local storage. The copy button writes your public IP to the clipboard only when clicked; use caution with the clipboard on shared devices.

If the interface is unavailable or a field is missing, the page shows “Temporarily unavailable” instead of generating a substitute result. Checking again requests fresh data; previous results aren’t reused as the current status. For details, see the Privacy Policy.

First Month Free