See the public IP address used for this request. Check again after connecting to compare your browser’s exit IP. Other apps need to be checked separately.
Preparing to query JinVPN’s API.
These results describe your browser’s connection to JinVPN’s API. They do not cover every network request from your device.
Your exit IP is the source address seen by the server. If it changes after you connect, the exit address for this request has changed. Location is based on IP databases and may be affected by address allocation and database updates; it is not your device’s precise location.
The ISP is the network operator associated with your exit IP. It may show a data center or route provider rather than your local broadband provider. Proxy detection is only an indicator: no proxy detected does not prove that your request did not pass through one. If the API cannot determine the result, this page will show “Temporarily unavailable.”
With smart routing enabled, JinVPN and your destination website may use different routes. Open the service you actually need to use and check it there too. If your browser’s exit IP has not changed, check your routing rules, client connection status, and whether a separate proxy is configured in your browser.
Read the guide to checking your exit IP and DNS →Checking your exit IP is not the same as testing for DNS leaks. This page does not run a dedicated DNS probe, so your IP location alone cannot show whether DNS is working as expected or leaking.
Review the DNS and routing settings in your client, and confirm that DNS requests are handled as intended. Then check your browser’s Secure DNS settings. If the browser selects its own DNS service, its behavior may differ from your system settings.
If you use a dedicated DNS testing tool, review its privacy policy first. Run the test before and after connecting, then compare the DNS providers listed in the reports. If your client offers DNS logs, you can also use them to see whether requests follow the expected route. Remove account credentials and subscription links before sharing logs.
A difference between the DNS resolver’s location and your exit location does not necessarily indicate a leak. Public resolvers, caching, and routing rules can all cause differences. Check whether domains that should use your route are instead being resolved by your local network. After changing settings, reconnect and check again in the app you want to use.
JinVPN does not log queries. This page requests exit information only from JinVPN’s GeoIP API. It does not fall back to a third-party public API or save query history in your browser. The copy button writes your current IP to the clipboard only when you click it.
If the API is unavailable, the page will say so rather than guess. Before sharing a screenshot or submitting a support ticket, consider whether you should obscure your public IP address. See the Privacy Policy for details on how data is handled.