What these details mean
Public IP: check whether your connection is active
Your public IP is the address a website sees for this request. Note the result before connecting, then click “Check again” after you connect. If the address changes, this request is using a different route. If it doesn’t, first check that your client is connected and that your browser is routed through the proxy.
Country, region, and ISP: check where the IP is registered
Location data comes from IP geolocation databases; it is not your device’s real-time location. The ISP field shows the network provider or organization associated with the address, which may not be your current local internet provider. Database updates can lag, and a location result alone cannot confirm whether an AI tool or streaming catalog is available.
Proxy detection: an indicator, not a security verdict
This page displays “Proxy detected” or “No proxy detected” only when the interface explicitly returns a result. If the field isn’t provided, it shows “Temporarily unavailable.” No proxy detected doesn’t mean you aren’t using one, and proxy detected doesn’t mean your connection is at risk. This check can’t determine encryption status or anonymity.
How to check for DNS leaks
DNS translates domain names into IP addresses. A change in your public IP doesn’t mean DNS requests are taking the same route. If DNS requests still use an unexpected network path, check your DNS routing. This page’s GeoIP interface only checks your connection’s public IP; it can’t probe DNS resolvers, so it won’t report whether DNS has “passed.”
- Check your client mode. Make sure the expected proxy mode and DNS settings are enabled. With split tunneling, your browser and other apps may use different routes, so don’t assume the whole device follows the browser’s route.
- Check your browser settings. Review your browser’s Secure DNS or custom resolver settings and make sure they match your client’s DNS policy. If the browser selects its own DNS route, the results may differ from your system settings.
- Check your system’s DNS route. Review the current DNS configuration in your system network settings. For a closer look, check your client’s diagnostic logs or capture local network traffic to see where DNS requests actually go. Seeing a DNS address alone isn’t enough to determine whether there’s a leak.
- Check again after reconnecting. After changing settings, reconnect your client and retry the target website. If you use a separate DNS resolver test, interpret the results in light of your expected configuration; an unfamiliar resolver name alone doesn’t indicate a leak.
If you’re still unsure, open a support ticket and describe your client, connection mode, and the issue. Remove account details and subscription credentials from any logs first. For basic connection steps, see Guides; for protocol and route details, see the technical reference.
Lookup privacy and handling errors
VPNNeed does not log lookups. This page only sends requests to VPNNeed’s GeoIP interface; it doesn’t use third-party public lookup services or save results in your browser’s local storage. The copy button writes only your public IP to the clipboard when clicked; it doesn’t copy any other fields.
If the interface is unavailable, a request times out, or a result is missing, the relevant field shows “Temporarily unavailable.” No sample address is inserted and no previous result is reused. This means the current lookup didn’t complete; it doesn’t mean your connection is down. Try again later, or visit the target service directly to check connectivity.
Your IP address may reveal your approximate network location. Before sharing a screenshot, hide any details you don’t want to make public. See the Privacy Policy for details on lookup practices and account information.