VPNQW / Network Check Notes

Public IP & Network Test

See the public details for this browser request. Run the check again after connecting to compare locations. Results do not reflect the connection status of every device.

Current connection details

Same-site lookup

Waiting for connection details.

Public IP
Temporarily unavailable
Country / region
Temporarily unavailable
ISP / network provider
Temporarily unavailable
Proxy detected
Temporarily unavailable

Location and proxy status are based on information returned by the endpoint. Fields that are not returned will show “Temporarily unavailable”; they are not inferred from other fields.

What these results mean

Check your public IP first, then consider what you need it for. A location change, a proxy label, and actual access to a service are different things.

Public IP: where this request comes from

This is the public address observed by our endpoint, not your device’s local address on a home network. After switching routes, select “Check again” to compare. If your client uses split tunneling, requests to this site may still go through your local network.

Location and ISP: useful reference data

Country and region are generally based on IP address databases. The ISP field may show a carrier, data center, or network provider. Database updates can lag, so the displayed location may not match your device’s actual location—and does not confirm that a particular streaming catalog will be available.

Proxy detection: a label, not proof of a connection

“Proxy detected” means the endpoint has flagged this public IP. “No proxy detected” means it did not identify that flag in this check. Neither result alone proves that encryption is active, that every app is using a proxy, or that a particular service will accept this IP.

DNS Leak Check

This page checks your public IP; it does not run an automatic DNS leak test. A changed public IP does not mean DNS requests are taking the same route.

  1. Record your public IP before and after connecting. If your network allows, compare the results from before and after connecting to check whether the selected location matches the details shown for your public IP. Don’t rely on the client’s connection icon alone.
  2. Review your client’s DNS and split-tunneling settings. Check whether the client handles DNS resolution and whether any rules bypass the proxy. Options vary by client; refer to the instructions in your dashboard for the specific steps.
  3. Check your browser’s secure DNS settings. A browser may use its own DNS resolver, independently of your system settings. Note the current configuration and compare it with your client’s recommendations. There’s no need to switch to an unfamiliar resolver just to test.
  4. Run a separate test if you need to verify the DNS route. Choose a trustworthy DNS test tool with a clear privacy policy, then check whether the resolver matches your expectations. A different DNS provider or location does not automatically mean there is a leak; consider your routing rules, encrypted DNS, and intended setup.

If your public IP doesn’t match expectations, first confirm that the client is connected, the route is selected, and this site isn’t set to bypass the proxy. Then run the check again. If you still have questions, submit a support ticket with your client platform, selected location, and a description of the issue. Don’t include subscription links or account passwords.

For setup steps, see Guides. For route types and location details, see the Nodes page. These results cannot replace testing access to the destination website itself.

Privacy Note

Queries are not logged. This page uses a same-site endpoint and does not fall back to a third-party public API if a check fails. Results remain on the current page and are not saved to browser storage.

The copied IP will be placed on your device’s clipboard. Check for your public IP and other account details before sharing a screenshot or submitting a support ticket. For details about data handling, read our Privacy Policy.

Start Free