Public IP Lookup
See the network egress address detected when this site receives a request from your browser. Switch routes, then run the check again to compare results.
Current Request Results
- Public IP Address
- Temporarily unavailable
- Country or Region
- Temporarily unavailable
- Internet Service Provider (ISP)
- Temporarily unavailable
- Proxy Detected
- Temporarily unavailable
What This Information Means
Public IP address is the internet-facing address this site sees, not your device’s local network address. Multiple devices on the same network can share one public IP. With split tunneling enabled, other sites and apps may use a different egress route.
Location and ISP details come from IP databases and reflect registered or inferred information, not your device’s actual location. On an international route, the ISP shown may be the network provider at the exit server rather than your local broadband provider.
Proxy status depends on whether the lookup service can identify the current address. “Not detected” does not mean your connection isn’t using a proxy. “Temporarily unavailable” means the service couldn’t provide a conclusive result.
Check for DNS Leaks
Your public IP and DNS routing are separate. Even if web traffic uses a different egress route, DNS queries may still be handled by your local network or a resolver configured separately in your browser. This page checks your public IP; it does not directly test for DNS leaks.
- Before connecting, check the DNS settings in your system’s network configuration and see whether your browser has Secure DNS enabled separately. Note the current resolver for comparison.
- After connecting, check your client’s DNS settings and split-tunneling rules. If the client provides connection logs, visit a domain that hasn’t been resolved yet in the same browser, then check whether the query followed the expected DNS route.
- If your rules require DNS queries to go through the tunnel but the logs show them going to a resolver on your local network, check the client’s DNS interception settings and your browser’s Secure DNS settings, adjust them, then test again. Seeing only your router’s local network address, having no logs, or finding a DNS server that differs from your public IP isn’t enough on its own to confirm a leak.
For help checking subscription or split-tunneling settings, see the complete guide.