Network check · Current browser IP

Public IP check

See the address and location your connection presents to websites. Check again after connecting or switching routes to compare the results.

Current public IP details

Checked via our API

Retrieving public IP details.

Public IP
Checking
Country / region
Checking
Internet service provider (ISP)
Checking
Proxy detected
Checking

These results reflect the public IP for this browser request only, not the connection route used by every app on your device. If proxy detection is unavailable, we won’t infer a result.

What these results mean

Public IP and location

The public IP is the address our API sees as the source of your request. It isn’t your device’s address on your local network. When network acceleration is enabled, your public IP will usually change if your browser traffic goes through the selected route.

Locations are based on IP geolocation databases, which may be out of date or use different regional labels. They don’t show your device’s actual location. If the result doesn’t match your selected region, check both your client route and browser traffic rules.

ISP and proxy detection

The ISP usually indicates the network organization associated with your public IP. It may show a carrier, data center or cloud provider rather than your local broadband provider.

“Proxy detected” is a result reported by the API, not definitive proof that your connection is working. “No proxy detected” doesn’t prove that your request wasn’t routed through a proxy, and it can’t be used on its own to assess privacy protection.

How to check for DNS leaks

DNS translates domain names into IP addresses. A changed public IP doesn’t mean your DNS requests follow the same route. This page checks only your public IP; it doesn’t run a DNS leak test, so it can’t confirm that there are no leaks.

  1. Check your client’s DNS settings

    Check whether your client handles DNS requests and whether your current traffic rules route them through your connection. Setting names vary by client; refer to the instructions in your dashboard.

  2. Check your system and browser settings

    Review your system DNS settings and your browser’s Secure DNS settings. A custom browser resolver may use a separate route. Note your original settings before making changes so you can restore them if needed.

  3. Compare DNS results before and after connecting

    If you use a dedicated DNS testing tool, compare the resolver’s operator with the route you expect. If a local resolver still appears after connecting and that doesn’t match your configuration, check your traffic rules and DNS handling settings.

Privacy and usage limits

We don’t log queries. Checks use an API on our own domain. This page doesn’t save query history or store results in your browser, and it won’t switch to a third-party public API if ours fails.

Your IP address may be associated with the network you’re currently using. Before sending screenshots or ticket details to others, mask the address if needed. The copy button copies only your public IP; it won’t send or share it.

An API error means this check couldn’t be completed; it doesn’t mean your current route is unusable. Try again later, or check your connection using the Getting Started guide. See our Privacy Policy for details on data handling.

Start Free