Same-origin lookup

Current public IP lookup

See the address, location, and ISP currently visible to websites. Run the lookup before and after connecting to a route to check whether your public location changes with the connection.

Public IP Location ISP Proxy status
Lookup results

Your network’s public details

The lookup starts automatically when the page opens. Results come from JNVPN’s same-origin GeoIP endpoint; if it is temporarily unavailable, the page shows a clear failure state instead of filling in data from a third-party public API.

CURRENT NETWORK

Lookup overview

Checking

Retrieving your current public details through the JNVPN endpoint.

IP address
Loading
Country or region
Loading
ISP
Loading
Proxy detected
Loading

Understanding the result

What these public details mean

An IP lookup shows the public network exit point visible to a website at that moment. It is not the device’s local network address and does not, by itself, describe your complete privacy status.

IP

Public address

Your public IP is the address visible when the device accesses the internet. After connecting to a JNVPN route, run the lookup again. If the address and location change with the selected route, web traffic is generally being sent through the new exit point. Reload this page after switching routes so an earlier cached state is not mistaken for the current result.

LOC

Country or region

Location data comes from IP address databases and represents the region where the address is commonly registered or identified. It is useful for checking the exit direction, but database updates can lag, and city-level details may differ from the data center’s actual location. To confirm that a connection is working, consider both whether the IP changed and whether the target service is accessible.

ISP

ISP

The ISP field shows the network organization or carrier associated with the public address. Before connecting, it often identifies the local access network; afterward, it may show a data center or route operator. Organization names can vary slightly between databases, so a change is best treated as supporting evidence rather than conclusive proof of a connection.

CHK

Proxy detection

Proxy detection is a reference result based on the address’s attributes. “Detected” does not necessarily indicate a connection problem: some data center exits may be classified as proxies. “Not detected” does not mean every request follows the same path. If you need to troubleshoot, also check DNS requests and your app’s traffic-routing settings.

Connection check

How to check for DNS leaks

Web traffic and domain resolution can follow different paths. Even after your public IP changes, confirm that DNS requests are being handled by the network environment you expect.

A DNS leak generally means web requests are using an accelerated route while domain resolution is still handled by the original access network. This can create inconsistent location signals and may cause some sites to load slowly, request repeated verification, or show content that does not match the exit location.

  1. Record the initial result

    Connect to the target route, refresh this page, confirm that the IP address and country or region fields have updated, and note the exit direction shown.

  2. Check the DNS resolver’s network

    Use the network diagnostics provided by your operating system, browser, or router to see which DNS servers are in use. If the resolver still clearly belongs to the original access network while your public exit has changed, continue by checking the client’s DNS and traffic-routing settings.

  3. Rule out caching and split routing

    Disconnect and reconnect to the target route, close pages that may retain earlier DNS results, and run the checks again. If only a specific app behaves differently, confirm whether that app is excluded from the route.

  4. Choose an approach for your situation

    When a unified public exit is needed, enable DNS handling or a global connection setting suited to the current network in the client. When local service access must be preserved, review the split-routing rules so essential local resolution is not sent through a remote route.