What This Information Means
Public IP and Location
The public IP is the source address seen by this site's API, not your device's address on the local network. Check it before connecting and save the result, then check again after connecting to your chosen route. Comparing the results can help confirm whether your browser traffic is using that route. Split-tunneling rules may send requests to this site over your local network. If the result hasn't changed, check your client's mode and rules first.
The country or region is an estimate based on an IP geolocation database, which may be outdated or differ across providers. It doesn't indicate your device's physical location, nor does it prove that a particular streaming service or AI tool is accessible. Platforms may also consider your account region, payment details, and their own risk checks when deciding access.
ISP and Proxy Detection
The ISP field usually identifies the network provider or hosting network associated with the public IP; it may not be your local broadband provider. “Proxy detected” means the API has flagged the IP as associated with a proxy. “No proxy detected” only means this API didn't return a proxy flag for this request; other websites may reach a different conclusion. If the API returns no clear result, this page won't speculate.
Still having issues after connecting? Check the import and connection steps in the Quick Start Guide, or see Frequently Asked Questions for troubleshooting tips.
Check for DNS Leaks
DNS translates domain names into network addresses. If your web traffic uses an international route while DNS lookups still follow your local network settings, the two types of requests may take different paths. Browser Secure DNS, operating system settings, and your client's DNS rules can all affect how lookups are routed.
- Check your client settings. Review the connection mode, routing rules, and DNS configuration. If your client records DNS requests, visit the domain you want to check, then see which rule handled the lookup and which DNS resolver received it.
- Check your operating system and browser. See which DNS server your current network connection uses and whether Secure DNS is enabled in your browser. Browser settings may differ from your client's configuration, so consult the client documentation to confirm what to expect.
- Verify after reconnecting. Save your changes, reconnect as directed by your client, reopen the website, and review the DNS request records. If needed, clear your operating system or browser DNS cache so old results don't affect your checks.
- Tell different issues apart. A domain failing to resolve, a website connection timing out, and a platform showing a region notice are different issues. Note the affected domain, client mode, and error message, then submit those details through a support ticket in the user panel.
These steps help you verify your settings. If you can't access actual DNS request records, treat the result as unconfirmed; a website loading successfully alone doesn't prove there is no DNS leak.
Query Privacy and Error Messages
Queries are not logged. This page requests public IP information only from VPNPB's GeoIP API. It doesn't contact third-party public lookup APIs or save results in your browser's local storage. Clicking Copy writes the current public IP to your clipboard so you can save or check it yourself.
If the API times out, the network disconnects, or the response can't be read, this page shows “Temporarily unavailable” and lets you try again. Check your browser's network connection and, if needed, switch routes before retrying. A failed lookup alone doesn't mean your client connection has stopped working.
Before sharing a screenshot or submitting a support ticket, check that it doesn't contain subscription links, account credentials, or other sensitive information. See the Privacy Policy for details.