Public IP Lookup

Public IP: the address used for this request

Websites see the exit address your request uses after network routing, not your device’s local network address. Compare the IP shown here before and after connecting to VPNJiage. If your browser still uses a direct-connection rule, this result may not change even when your client says it’s connected.

Location and ISP: network details from IP databases

The country or region and ISP come from the IP location data returned by the API. They describe the exit network, not your device’s precise location. Changes in IP assignments, delayed database updates, and differences in ISP naming can all affect what appears. If a field isn’t returned, we’ll show “Temporarily unavailable” rather than guess based on the IP.

Proxy detection: an indicator, not proof of connectivity

We show a proxy detection result only when the API explicitly returns a proxy flag. “No proxy detected” doesn’t mean the request is definitely direct, nor does it prove how private the connection is. Likewise, “Proxy detected” doesn’t guarantee that a particular streaming service or AI tool will work. Platforms may also consider account region, payment region, and their own risk controls.

If the result doesn’t match: First check the active route in your client, then confirm that browser traffic is covered by its proxy rules. Temporarily disable other extensions that might change your exit IP and run the check again. Then test the connection with the service you actually need. See the quick start guide for setup steps and the server guide for route details.

This page checks your public IP; it does not run an active DNS leak test. DNS translates domain names into network addresses, and DNS requests may take a different path from web traffic. Your public IP, location, or proxy status alone can’t show whether DNS is using the route you expect.

1. Check your client’s DNS and routing settings. Confirm whether the client handles DNS resolution and which requests connect directly in rule-based mode. Options vary by client, so don’t rely on the connection toggle alone.
2. Check your browser’s secure DNS settings. A browser may select its own DNS resolver, creating a different path from your system or client. Note your current settings before making changes, and follow your client’s instructions. Changing several options at once can make the cause harder to identify.
3. Use your client’s diagnostics to check the DNS path. If your client provides DNS logs or connection records, use them to review the rules and exit route applied to domain requests. A difference between the DNS provider’s name or location and your exit location does not, by itself, prove a leak.
4. Submit a support ticket if you need further help. Include your operating system, client, connection mode, and a description of the issue. You may attach screenshots with sensitive details obscured. Do not share passwords, full subscription links, or other credentials.

A successful IP lookup only confirms that this request completed; it does not mean your DNS is secure. If the DNS path is unclear, keep your current results and submit a support ticket in the user panel →