Current IP Lookup
See the network route your browser uses to access this site. After connecting or switching routes, run another lookup to compare the results.
Connection details
Lookup via XixiVPN APIGetting ready to check your current connection.
- Current IP address
- Waiting for lookup
- Country / region
- Waiting for lookup
- Internet service provider (ISP)
- Waiting for lookup
- Proxy detected
- Waiting for lookup
Results reflect only this browser request and may not match the network route used by other apps. This page does not run an automatic DNS leak test.
What this information means
Check your connection route before troubleshooting access issues. IP geolocation and proxy detection are reference points only.
IP address and location
The public IP address is the one seen by this site’s API when it receives your request—not your device’s address on the local network. Once connected to a route, your browser will generally show its public IP if the request passes through it. Location data comes from an IP database and may differ from the city listed for a route or the provider’s registered address. It does not confirm your device’s actual location.
ISP and proxy detection
An ISP usually identifies the network operator associated with the public IP address. The result may show a data center or upstream network and may not match your subscription provider’s brand. Proxy detection relies on classifications supplied by the API: “No proxy detected” does not mean your request wasn’t routed through a proxy, and “Proxy detected” alone does not indicate whether the connection is secure. If the API doesn’t return this field, this page will say it’s temporarily unavailable.
Results unchanged after switching routes
First, make sure your client has applied the new route, then select “Run lookup again.” In rule mode, requests to this site may still use your local network; other apps may follow different routes. Check your client’s routing logs rather than assuming every app has switched its connection.
For help checking your settings, see the Getting Started Guide. For the difference between regions and route types, see the Route List.
DNS leak check
A public IP lookup and a DNS test are different checks. Your IP address alone can’t confirm whether DNS is leaking.
DNS translates website domain names into IP addresses. If you expect domain lookups to use your selected route but they’re handled by an unexpected resolver, investigate further. A DNS provider’s registered location differing from your public IP’s location is not, by itself, evidence of a leak.
- Check your client’s DNS routing. Review DNS settings and connection logs to see whether queries use client-managed DNS, system DNS, or a specified resolver. In rule mode, DNS queries and website requests may follow different rules.
- Check your system and browser settings. Browser Secure DNS, encrypted DNS in your operating system, and other networking tools can override the DNS route your client is expected to use. Note your current settings, then check them one at a time so you can identify the cause.
- Distinguish cached results from new requests. Old DNS cache entries can hide changes to your settings. Follow your operating system or browser’s instructions to clear the cache and reconnect, then check the DNS request route in your client’s logs.
- Don’t draw conclusions without enough evidence. If the logs don’t show where DNS queries went, you can’t confirm whether a leak occurred. In the user panel, submit a ticket with your operating system, client settings, and a description of the issue. Before sharing screenshots, redact subscription URLs and account credentials.