Public IP check

What these results mean

Compare your public IP before and after connecting

Your public IP is the address seen by this site’s API. After connecting to VPNJL, select “Check again” to see whether your IP and country or region have changed. If your browser traffic is routed through your selected connection, the public IP will usually change. Split tunneling, browser proxy settings and your local network can all affect the result.

The country or region is based on an IP geolocation database, not your device’s physical location. Database updates may be delayed, and the result may differ from the region shown for a route in your client. ISP identifies the network operator associated with the address; seeing a data center or network company name does not mean your connection has a problem.

Treat proxy detection as a guide

The proxy field displays the result returned by the API. “No proxy detected” means the API didn’t identify proxy indicators for this check; it is not a guarantee of anonymity or privacy. “Proxy detected” doesn’t mean the route is faulty. If the API provides no clear result, this page shows “Temporarily unavailable” rather than treating missing data as a negative result.

A changed public IP only shows that the route for this request has changed. Check streaming availability and whether other apps use the proxy separately in each service or app.

DNS leak check

DNS translates domain names into network addresses. A public IP lookup can’t show all DNS requests, so this page doesn’t run an automatic DNS leak test or declare a pass based on your IP location.

1. Open the client’s network or DNS settings, confirm the connection mode, and check whether its DNS interception feature is enabled. Available options depend on the client version and interface.
2. Check your browser’s Secure DNS settings. A DNS resolver selected in the browser may use a different route from your system or client, so review it alongside your split-tunneling rules.
3. Compare your system’s DNS settings and the client’s diagnostics before and after connecting. Resolver addresses in the configuration are clues; check the actual request path to determine whether traffic goes through the tunnel.
4. If settings don’t match expectations, save the client’s connection mode, DNS settings and error details, then open a ticket in the user panel. Don’t include your password or full subscription link.

A local network resolver appearing in your settings doesn’t necessarily indicate a leak. Using a remote resolver doesn’t automatically mean requests travel through the tunnel. Check the configuration, actual routing and app behavior together.

For help checking your connection setup, see the Getting Started Guide. For assistance, visit the support ticket panel.