Public IP Lookup

What this information means

Your public IP is the address this site sees

Your public IP is usually an address provided by your ISP or selected route, not your device’s local network address. Check it once before connecting, then run the lookup again after connecting to your chosen route to see whether your browser’s public IP has changed. If you use app-based or domain-based routing, this site may connect directly while the app you’re checking uses a proxy. Check your client’s rules rather than assuming the connection failed because the address stayed the same.

Location and ISP are clues, not proof

Location data comes from IP geolocation databases. It does not show your device’s actual location or necessarily match the region a website assigns to your account. Database updates may lag. The ISP field may show an internet provider, data center, or organization associated with the address; it’s common for this name to differ from the route name. If the location looks wrong, check your selected server and routing rules, then verify in the service you’re using.

Proxy detection does not confirm a successful connection

Proxy detection relies on the lookup provider’s assessment. “Proxy detected” means the address was identified as a proxy; “No proxy detected” does not mean all traffic is going direct. If the endpoint returns no clear result, this page will show “Temporarily unavailable” rather than guess. This check does not prove anonymity or guarantee that AI tools or streaming services will work.

DNS leakcheck

DNS translates domain names into network addresses. A public IP lookup only shows the source of this web request; it cannot see every DNS request from your device. This page does not run a separate DNS leak test, so a public IP that looks right does not confirm that your DNS settings are correct.

1. Check your client’s DNS settings. See whether the client handles DNS resolution and whether DNS requests follow your selected route as expected. Refer to the documentation for your client’s current settings, and avoid enabling conflicting DNS policies at the same time.
2. Check your browser and system settings. Browser Secure DNS, custom system resolvers, or other networking tools may change how DNS requests are routed. Note your current settings, then check them against your client’s documentation. Don’t disable all protections just to troubleshoot.
3. Recheck with the same rules in place. Record the resolver information before and after connecting. If you use a separate DNS testing tool, focus on the resolvers it detects rather than just the public IP used for web requests. A resolver in a different region may also be part of the service’s distributed network.
4. Keep troubleshooting details if the results are unclear. Note your operating system, client name, selected route, routing mode, and DNS settings so support can review them. Hide account details and subscription URLs before sharing, and never post your full configuration publicly.

Privacy notice

Queries are not logged. This tool gets current connection details through a same-origin endpoint and does not fall back to a third-party public API if the lookup fails. Results are displayed only on this page. Copying is initiated by the user, and lookup history is not saved automatically.

An IP address may still reveal the organization behind a connection or an approximate location. Share only what’s needed when sending screenshots or troubleshooting notes. VPNIW describes its privacy approach as “anonymous, no logs.” See the privacy policy for details on data handling.