See where this request connects to the internet from. Run the check again after switching routes to see whether your browser’s public IP has changed.
Results apply only to requests sent to this site’s lookup interface. They don’t show the connection route used by every app.
Waiting for lookup. Enable JavaScript to check automatically.
Copies only the public IP address, not the other lookup details.
Location and proxy labels come from the lookup interface and may not reflect the latest data. Missing fields are left blank rather than estimated.
A change in public IP, a location label, and proxy detection are separate signals. Consider each on its own.
This is the public IP address seen by VPNBody’s interface, not usually your device’s address on your local network. Check it before and after connecting to a route. If it hasn’t changed, first make sure your client is connected and that traffic to this site isn’t routed through your local network.
Different apps may use different proxy settings. A successful browser check doesn’t confirm how command-line tools, IDEs, or other clients are routed.
The country or region comes from an IP address database; it isn’t your device’s location. The registration details, actual use of an address, and database update schedule can all differ, so the location label may not match your expectations.
The ISP field may show a data center or network operator rather than VPNBody. Other websites may use different databases and report a different location.
“Proxy detected” means the lookup interface returned a proxy label for this address. “No proxy detected” means only that this response didn’t include that label; it doesn’t prove the connection isn’t using a proxy.
This field can’t establish your level of anonymity or guarantee access to an AI tool or streaming platform. If the field isn’t returned, the page shows “Temporarily unavailable.”
This page checks your public IP; it doesn’t run an automated DNS leak test. A matching public IP location doesn’t tell you which DNS route is in use.
DNS translates domain names into network addresses. If you want domain lookups to follow your client’s connection, first check its DNS settings and routing rules. Some rules send specific domains to local DNS resolution. That’s a configuration choice to assess in context—not proof of a leak based solely on where the resolver is located.
ipconfig /all in a terminal; on macOS, run scutil --dns; on Linux systems using systemd-resolved, run resolvectl status. These commands show your local configuration but don’t, by themselves, prove where queries ultimately go.If you still can’t determine what’s happening, contact us through the support ticket panel and include your platform, client settings, and a description of the issue. Before sharing screenshots, hide account details and subscription links. Don’t send passwords or full subscription URLs.
We don’t log lookups. Checks query only VPNBody’s own interface and won’t switch to a third-party public lookup service if it fails. Results aren’t saved in your browser’s local storage. Copying happens only when you click the button.
Your public IP is network information, so consider why you’re sharing it. If you’re connected through a proxy, this page will usually show the proxy’s public IP, not your device’s original public IP.