Current Public IP

Public IP: The address this site sees

This is the public IP address seen by this site when your browser request reaches the lookup endpoint. If you use a proxy and your browser traffic goes through the selected route, the result may show that route’s exit IP. With split tunneling, this site may use your local network instead. An unchanged result does not mean that no apps are using a proxy.

Country, Region, and ISP: Information from IP databases

Location data usually comes from IP address databases. It is not device geolocation and cannot prove a server’s exact physical location. The ISP field may show the data center or upstream network associated with the exit IP, rather than your current internet provider. IP assignments and database updates can differ, so check your client’s route details if the information doesn’t match.

Proxy Detection: A result with limitations

This page displays “Proxy detected” or “No proxy detected” only when the lookup service provides a clear result. If the status is unknown, it remains “Temporarily unavailable.” Shared exit IPs, data center addresses, and database coverage can all affect detection. No proxy detected does not prove that traffic is going direct, and proxy detected does not mean the connection is faulty.

How to compare: Keep the current result, switch to your intended route, then click “Check Again.” Also test the service you actually need to access; an IP lookup alone cannot confirm app connectivity.

DNS translates domain names into network addresses. Even when web traffic goes through a proxy, DNS requests may be handled separately by your browser, operating system, or local network. So a changed public IP does not prove that DNS requests use the same route.

1. Confirm the expected route. Check whether your client is using split tunneling or global mode, and whether it handles system DNS. Domains set to connect directly may use local DNS; that is not necessarily a problem.
2. Check your browser settings. Review the browser’s Secure DNS or encrypted DNS settings. A DNS service configured in the browser may differ from your system settings. Don’t disable security features just to make the results appear consistent.
3. Review client DNS logs. If your client provides DNS query records or connection logs, check which resolver handled the domain and which rule applied. Before sharing logs, remove account details, subscription URLs, and browsing activity.
4. Use independent tests as supporting evidence. If you use a DNS testing tool, review its privacy policy first, then compare the reported resolver with your expected setup. A resolver showing a different location does not, by itself, prove a leak; check whether DNS requests bypassed the intended route.

If you can’t confirm your settings, note the connection mode, client platform, and what happened before changing anything. Then ask for help through the user panel ticket system. For setup instructions, see the getting started guide; for common connection issues, see the FAQ.

Lookup data is not logged. Checks use an endpoint on this site; this page does not fall back to third-party public lookup services or save results in browser storage. When you click Copy, only your public IP is copied to the clipboard.

If the endpoint is unavailable, your network is interrupted, or the response is missing fields, the relevant value will show “Temporarily unavailable” rather than an estimate. Check your connection and try again, or switch routes and retry. A failed lookup does not, by itself, mean your proxy is not working.

An IP address can reveal information about your network. Before sharing a screenshot, cover any address details you don’t want to make public. For details on how service data is handled, see the Privacy Policy.