Connection Check

Current Public IP Lookup

See the public IP used by this browser request. Check again after connecting to a route, then compare the results.

Public IP Details

Same-Site Lookup

Loading public IP details…

Public IP
Checking…
Country / Region
Checking…
Network Provider / ISP
Checking…
Proxy Detected
Checking…

Results apply only to this browser request, not every app on your device. Proxy detection does not show whether your route is connected.

How to Interpret These Results

A change in your public IP can help verify a connection, but interpret the results alongside your client and app settings.

IP Address and Location

The public IP is the address the interface sees for your request, not your device’s local network address. Location comes from an IP database and may differ from the route name or the data center’s actual location. It cannot pinpoint your exact location.

ISP and Network Ownership

The ISP field may show a carrier, hosting provider or network organization. After connecting to an international route, the name may not mention VPNZW. Check the public IP, target region and client status together.

Limits of Proxy Detection

Detection depends on the interface’s data sources. A proxy detected result does not mean your connection is faulty, and no proxy detected does not prove your request did not use a proxy. If the interface cannot determine the result, this page will say so.

DNS Leak Check

An IP lookup and a DNS check are different. This page does not actively test your DNS resolution path or report a “passed” result.

DNS translates domain names into addresses used for connections. If web traffic uses your selected route but DNS queries follow an unexpected path, investigate further. A correct public IP does not mean your DNS settings match expectations.

  1. Check your client’s DNS settings. Confirm that DNS interception, system proxy or tunnel mode is enabled as described for your client. In split-tunneling mode, local resolution for some domains may be expected by the rules; check the destination first.
  2. Check your browser’s DNS settings. Secure DNS in your browser may use settings independent of your system. Make sure they match your client setup so you don’t overlook a separate browser setting.
  3. Verify the path using local information. Check your system’s active resolver and your client’s DNS logs. If your system shows a local forwarding address, confirm where it forwards requests. To investigate further, use a trusted DNS test tool and read its privacy policy first.
  4. Verify again after making changes. Follow your client’s instructions to clear the cache and reconnect, then check the target website. If you still have questions, note the setting names and describe the issue without sensitive details, then submit a support ticket through the user panel.

This page does not open external test sites automatically. Seeing only the system resolver’s name is not enough to confirm which route DNS requests take.

Privacy and Query Scope

We do not log queries. Requests are sent only to VPNZW’s same-site GeoIP interface, with no third-party public API fallback. The copy button writes the public IP to your clipboard only when clicked.

An IP address is network identifier information. Consider masking the full address before sharing a screenshot. Don’t include passwords or subscription links when sending information to support.

View Privacy Policy →