Reveal the public IP address the internet sees, plus geolocation hints and request headers. Use the browser tool or curl to confirm your VPN exit node.
Run this in a terminal. With a VPN connected, the returned IP should match the VPN exit — not your ISP.
curl -s https://rookvpn.com/check/api/ip/addressSplit tunneling can route the browser through the VPN while curl uses the local interface (or the reverse). Always compare both when diagnosing leaks.
Your public IP reveals approximate location and ISP. Trackers correlate it with cookies and fingerprints — a VPN only helps if the exit IP is what every app actually uses.
Check Your Public IP Address exists to report the public IP address and network your browser is using right now. It is not a second copy of the tool homepage. The homepage introduces the whole product. This page stays on one job so a search for that job lands on instructions you can follow without hunting through other tabs. Read the result on this page against the input you actually used. A screenshot without the input is not evidence. If the result surprises you, change one thing and run it again before you change your VPN, browser, or server config.
Work through Check Your Public IP Address in order. 1. Open the public IP tab and read the address, ASN, and location label. 2. Run curl against the same IP endpoint in a terminal. 3. If the two addresses differ, find the app that is split-tunneled. 4. Reconnect the VPN and refresh both. Write down the input and the output together. When you ask someone for help, send both. Repeat the same input once. A stable tool returns the same answer. If it does not, the input changed or the page is talking to a different network path than you think.
Geolocation from an IP is a city-level guess from a registry, not your street address. The IP is the exit the site sees, which may be a VPN, a carrier NAT, or your router. Treat the output as a measurement, then decide. RookVPN does not log the contents of a client-side tool, and a measurement is not a promise that every other app on the device behaves the same way. Compare a second path when the decision matters: a terminal command, another browser, or the matching guide linked below.
Example: the browser shows 203.0.113.10 and curl shows 198.51.100.4. The browser is on the VPN and the terminal is not, or the reverse. Align them before you debug a website that only misbehaves in one of those two places.
After you finish Check Your Public IP Address, open the WebRTC leak test if the IP looks right but a site still knows your home network if the next question is different from the one this page answers. Stay here if you are still on the same job. Extra pages help only when they answer a new question, such as a different algorithm, a different leak channel, or a different file type. The documentation link on this page is the long form of the same workflow, including the checks that do not fit in the tool UI.
Use: curl -s https://rookvpn.com/check/api/ip/address — or open rookvpn.com/curl to run it online.
Different apps can use different routes. On mobile or with split tunneling, browser traffic may use the VPN while the terminal does not.
It is the public address of whatever network is carrying this browser. A VPN replaces it with the exit address.
IP location databases are coarse. A VPN exit is often labeled as the datacenter city.
On one computer with one default route, they should. A mismatch means split tunneling or a proxy on only one app.