KekeVPN Public IP Lookup
See where your requests are routed, then check whether the site you want to use is accessible. After connecting to a route, run the check again to compare your public IP.
Current Connection Details
Waiting for lookup- Public IP
- Temporarily unavailable
- Country / Region
- Temporarily unavailable
- ISP
- Temporarily unavailable
- Proxy detected
- Temporarily unavailable
Results reflect only the public IP used for this browser request. Location and proxy status come from the API response; they don’t indicate your device’s actual location or show whether all your apps use the same route.
What this information means
Public IP: the address websites see
Your public IP is the address used for this request. Check it before and after connecting to KekeVPN, and note the results. If it changes, this request is using a different public IP. If it doesn’t, first check the client’s connection status and whether your browser is covered by a direct-connection rule.
The address may also stay the same if the route uses a shared public IP. This page can’t show how traffic from every app is routed, so check within the apps you actually use.
Location and ISP: clues about the public IP
Location reflects how an IP address database classifies the public IP; it isn’t device geolocation. Database updates may lag, and different sites may report different locations. ISP usually identifies the network operator associated with the address, which could be an access provider, data center, or cloud network—not the network your device is currently connected to.
Proxy status: an indicator, not a connection verdict
“Proxy detected” means the API has labeled the current public IP as a proxy network. “No proxy detected” only means the API didn’t return that label; it doesn’t confirm how traffic is routed or whether your connection is private. If the API doesn’t explicitly return this field, the page shows “Temporarily unavailable” rather than treating a missing value as a negative result.
Check for DNS leaks
DNS translates domain names into network addresses. Routing web requests through your selected route doesn’t guarantee that DNS queries take the same path. This page checks only the public IP used for HTTP requests; it doesn’t run a separate DNS leak test, so it can’t report a pass or confirm a leak.
-
Check the client’s DNS settings.
Check whether the client’s DNS settings match your connection mode. Follow the client’s documentation, and avoid layering multiple DNS rules unless you understand what each one does.
-
Check your browser’s Secure DNS settings.
A browser may resolve domain names separately from your operating system. Note the current settings, then check the client’s documentation to make sure they work with your routing rules. Encrypted DNS alone doesn’t guarantee that queries use your selected route.
-
Check your system and other network tools.
Other proxy tools, browser extensions, or system network settings may affect how traffic is routed. Change settings one at a time and note the results, so you can identify the cause without changing several things at once.
-
Use DNS records as an additional check.
For a closer look, review the DNS diagnostics available in your client to see whether queries are handled as expected. A difference between the DNS server’s location and your public IP’s location doesn’t, by itself, prove a leak; consider it alongside your intended routing rules.
For help checking connection steps, read the Getting Started Guide. To learn about choosing a route, see the Route Selection Guide.
Query privacy and error messages
KekeVPN doesn’t log queries. Your browser retrieves connection details through KekeVPN’s own API without sending fallback requests to third-party lookup services or requesting device location access. Results stay on this page; your IP is copied only when you click “Copy IP.”
“Temporarily unavailable” may mean the API is down, the request timed out, or the response was incomplete. It doesn’t prove there’s a connection problem. This page won’t fill in results with sample addresses. Try again later, or first check that your current network can reach KekeVPN.
When sharing troubleshooting details, remember that an IP address may reveal information about your network. Share only what’s needed, and never post account passwords or subscription links. See the Privacy Policy for details on how your privacy is handled.