Current Browser · Public Network

IP Lookup & DNS Checks

Check your public IP first, then see whether your connection is working as expected. Results show only the network route used by this browser to reach VPNWB’s lookup API; they don’t reflect the connection status of every app.

VPNWB API lookup

Current network details

Public IP address
Temporarily unavailable
Country / Region
Temporarily unavailable
Internet service provider (ISP)
Temporarily unavailable
Proxy detected
Temporarily unavailable

Waiting for lookup. Enable JavaScript to check your current public IP and network details.

How to interpret these results

Public IP and geolocation

The public IP is the address seen by VPNWB’s API. Run the lookup again after connecting to VPNWB to see whether it changes. If your browser isn’t covered by the client’s proxy rules, the lookup may still show your original IP even when the client says it’s connected.

Country and region are based on IP geolocation databases, which may be out of date or vary in accuracy. They don’t show your device’s precise location or guarantee that a streaming platform will recognize the same region.

ISP and proxy detection

The ISP usually identifies the provider or network organization associated with the public IP, not necessarily the provider of your local internet connection. With a relay or dedicated line, those can differ; check your route settings to understand why.

Proxy detection is based on information supplied by the API. “Not detected” doesn’t mean you aren’t using a proxy. If the field is missing, it will show “Temporarily unavailable” rather than treating that as a negative result. It also can’t tell you how well your connection protects your privacy.

DNS Leak Checks

DNS translates domain names into IP addresses. A change in your public IP doesn’t mean DNS requests take the same route. This page only uses an IP geolocation API; it does not test for DNS leaks or provide a “passed” result.

  1. Check your client’s DNS settings. Make sure the DNS handling recommended for your client is enabled, and check whether your system proxy, routing rules or tunnel mode covers this browser. Setting names vary by client.
  2. Check your browser and system settings. Secure DNS in your browser, custom system DNS and other networking tools may use different resolution routes. Don’t assume there’s a leak based on a setting’s label alone; check that the settings work with your client’s configuration.
  3. Use a dedicated DNS leak test to assess the results. If you use a separate testing tool, review its privacy policy first, then compare the DNS providers shown before and after connecting. Public DNS services may use distributed egress, so results from different regions don’t necessarily indicate a leak. What matters is whether requests bypass the route you intended to use.
  4. Keep the troubleshooting context. If your public IP hasn’t changed as expected, first check which traffic is covered by the proxy, then review your DNS settings. For help, open a support ticket in the user panel and include the platform, client mode and issue details. Don’t send your password or full subscription link.

Lookup privacy and data handling

VPNWB doesn’t log lookups. Your browser sends a request only to VPNWB’s lookup API to retrieve current network details. This page doesn’t save results to local storage or use a third-party public lookup API if the request fails.

Clicking “Copy public IP” copies the current address to your clipboard. Before sharing screenshots or troubleshooting details, cover any IP address you don’t want to make public. See our Privacy Policy for details.

Start Free