NETWORK INSPECTION

Public IP & DNS Check

See the public IP used for your current web request. After switching routes, run the check again and compare the result with your client settings.

Current public IP details

Waiting for check

Enable JavaScript to retrieve your current connection details through the VPNEdit API.

Public IP address
Temporarily unavailable
Country / region
Temporarily unavailable
Network provider / ISP
Temporarily unavailable
Proxy detected
Temporarily unavailable

Only the public IP is copied; no other query details are included.

RESULT NOTES

What these results mean

Your public IP isn’t your device’s local address

The public IP is the address identified by the VPNEdit API when it receives your current request. It may belong to your local network or the route you selected; it isn’t your device’s address on your local network.

Split-tunneling rules may send your browser and other apps through different routes. This page can’t replace checking the connection within the app you want to use.

Geolocation is an estimate from databases

The country, region, and ISP reflect information associated with the IP address in geolocation databases, not your device’s precise location. IP allocations, database updates, and route selection can all affect the results.

The ISP may appear as a data center or upstream network. A name that differs from your local internet provider isn’t necessarily a sign of a problem.

Proxy detection has limitations

Proxy status comes from a detection field returned by the API. No proxy detected doesn’t prove your traffic isn’t routed through one; a proxy detected result doesn’t identify the client you’re using.

If a field is missing, it will show “Temporarily unavailable.” This page won’t infer proxy status from your IP address or location, or use it to judge whether your connection is secure.

DNS REVIEW

DNS Leak Check

A public IP lookup can’t directly detect DNS leaks. This page doesn’t run a dedicated DNS test or automatically label your connection as “passed” or “failed.”

A DNS check looks at whether domain lookup requests follow the network path you expect. A web request using your selected route doesn’t mean DNS requests take the same path. Your browser, operating system, and client may each handle DNS differently.

  1. Confirm the expected route. Check your client’s connection mode and DNS options to decide which apps and domains should use DNS over your selected route. Keep a record of the original settings so you can restore them.
  2. Check your system and browser. Review the DNS settings in your system’s network settings and the browser’s Secure DNS options. A DNS service configured separately in the browser may not follow your client’s rules. Don’t judge a DNS leak by the service name or location alone.
  3. Review client logs. If your client provides DNS or connection diagnostics, open the target website and check which rule matched the DNS request and what resolution path it used. If no logs are available, treat the result as unverified.
  4. Change one setting at a time, then check again. After each change, verify that the target website and your other apps still work. Before using a third-party DNS testing tool, review its privacy policy. Compare the resolver results with your intended settings rather than relying on whether the locations match.

If you need help, include your operating system, client name, connection mode, the issue you’re seeing, and the settings you’ve already tried. For client-specific steps, start with the getting started guide.

QUERY PRIVACY

Query privacy and data handling

VPNEdit doesn’t log queries. This page uses the VPNEdit API to retrieve network details for your current request and doesn’t fall back to a third-party public API. Results appear only on this page; copying writes only your public IP to the clipboard.

IP addresses are sensitive network information. Before sharing a screenshot with support, hide any addresses, account identifiers, and subscription links that aren’t needed. Never share your password or full subscription credentials. See the Privacy Policy for details.