Network Checks

Public IP Address Check

Check your current public IP, then compare it after connecting.

Current request's public IP

Results come from our lookup endpoint and reflect only this web request.

Waiting for results
Public IP address
Waiting for results
Country / Region
Waiting for results
ISP / Network Provider
Waiting for results
Proxy detected
Waiting for results

Preparing your lookup. Data that has not been returned will not be shown as a result.

After switching routes, select “Check again.” If your client uses split tunneling, this page may still connect over your local network.

What these results mean

Location, ISP, and proxy status each tell you something different.

Public IP: the address websites see

This is the public IP address identified when our endpoint receives your request, not your device's local network address. A change before and after connecting can indicate that your public IP has changed, but it does not prove that every app is using the same route.

Location and ISP: IP address records

Country, region, and ISP information comes from IP databases and may be out of date. The ISP field may show a data center or network provider rather than your local internet provider, and the listed location does not necessarily indicate your device's actual location.

Proxy status: an indicator, not a verdict

“Detected” or “Not detected” reflects the endpoint's result, not a complete security assessment. Databases can miss or misidentify proxies. If the endpoint does not provide this field, the page will say it is temporarily unavailable rather than assume no proxy is in use.

If your public IP has not changed as expected, first make sure your client is connected, then check whether your browser is covered by a proxy rule. Verify access to each service in the app where you use it.
Manual Checks

Check for DNS Leaks

A public IP lookup is not a DNS leak test.

DNS translates domain names into network addresses. This page does not run a dedicated DNS test or automatically determine whether a leak was detected. A changed public IP does not prove that DNS requests are using the expected route.

  1. Review your client's DNS settings. Check whether the client's DNS handling option is enabled and whether the proxy mode and split-tunneling rules suit your needs. Note your current settings before making changes, and follow the client's instructions.
  2. Check your system and browser settings. Secure DNS in your browser, encrypted DNS in your operating system, and other network tools may use different resolution paths. Check more than one setting, and don't disable security features just to test.
  3. Compare the actual DNS resolution path. If you use a dedicated DNS testing tool, review its privacy policy first, then check whether the detected resolver is expected. A difference between the resolver's location or name and your public IP does not, by itself, prove a leak; also consider your client's rules.
  4. Keep a record of your settings and symptoms. If you still have questions, note your platform, client mode, test results, and any relevant error messages, then submit a support ticket through the user panel. Before sharing screenshots, hide subscription links, account details, and any network addresses that aren't needed.

Privacy and lookup limitations

We do not log queries. Checks are sent only to our endpoint; we do not fall back to a third-party public API if a request fails. The copy button writes the current public IP to your clipboard only when clicked; it does not read clipboard contents.

If the endpoint times out, the network connection drops, or data is missing, this page will show “Temporarily unavailable.” Check your connection and try again. A failed lookup does not mean the route is unavailable, and a missing proxy field does not mean no proxy is in use.

Read the full details in our Privacy Policy. Before sharing results publicly, consider whether you need to disclose your public IP and ISP information.