Network Check · Current Browser Connection

Public IP and Location

See the public IP used for this request. Check again after connecting or switching routes to compare results. This may not reflect the route used by every app.

Current Results

Checked via VPNFish

Waiting for a check. Enable JavaScript to view your current network details.

Public IP
Temporarily unavailable
Country / Region
Temporarily unavailable
ISP / Network Provider
Temporarily unavailable
Proxy Detected
Temporarily unavailable

Shows the public IP for this request only; it does not test for DNS leaks. Proxy status is based on the API’s assessment and does not indicate your client’s connection state.

What These Results Mean

Public IP: Where Your Request Reaches Us From

Your public IP is the address seen by our lookup service, not your device’s local network address. If your request goes through the route you selected, the public IP will usually change when you connect to a proxy. With split routing, this site, AI tools, and streaming services may use different routes, so an unchanged IP alone doesn’t mean the connection failed.

Location and ISP: Reference Data from IP Databases

The country, region, and provider shown are based on database records for your public IP, not your device’s actual location. Database update schedules, IP transfers, and network routing can cause discrepancies. The ISP may show a data center or network provider rather than your local broadband provider.

Proxy Status: A Clue, Not a Verdict

“Proxy detected” means the API flagged the address as a proxy. “No proxy detected” only means the API didn’t return that flag; it doesn’t mean you aren’t using a VPN. If the API doesn’t return a clear result, this page shows “Temporarily unavailable” rather than treating an unknown status as a negative result.

DNS Leak Check

DNS translates domain names into network addresses. Even when web traffic uses a proxy, DNS requests may still go through your local network. This page’s IP lookup can’t see those requests, so it can’t confirm that your DNS isn’t leaking.

  1. Check your client’s DNS settings. See whether DNS interception is enabled and how the current rules handle local and proxied DNS requests. Enabling a system proxy alone may not cover DNS requests from every app on your device.
  2. Check your browser’s secure DNS settings. A browser may use its own DNS provider instead of following system or client settings. Note your current settings first, then compare them with your client’s guide. Avoid changing several options at once, or it may be harder to pinpoint the cause.
  3. Check the DNS route before and after connecting. If available, use system network diagnostics or a packet capture tool to see which network interface sends DNS requests. The DNS servers listed by your system don’t prove that requests actually pass through them.
  4. Troubleshoot the specific settings. If DNS requests aren’t routed through the proxy as expected, check your client’s split-routing rules, DNS interception, and system network settings. Reconnect after making changes, then test the app you want to use. Don’t judge whether DNS is leaking by the DNS server’s location alone.

To review your client settings, start with the Guides. If the connection still isn’t working, see FAQs for troubleshooting tips, or describe the issue in a support ticket.

Start Free