Curl-based IP checks verify what exit IP HTTP clients use. Combine with RookCheck WebRTC, DNS, and IPv6 browser tests for complete leak detection.
1) Run curl IP check with VPN off. 2) Connect VPN and run again — IP should change. 3) Open rookvpn.com/check/vpn-leak-test for WebRTC, DNS, and IPv6 browser tests.
VPN Leak Test with Curl exists to use curl as one part of a leak test, together with the browser checks curl cannot do. 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 VPN Leak Test with Curl in order. 1. Print the terminal IP with the command on this page. 2. Open the browser leak suite. 3. Compare IP, then still run WebRTC and DNS in the browser. 4. Do not stop after the curl line matches. 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.
Curl cannot see WebRTC candidates. Curl uses the terminal DNS, which may differ from the browser. A matching IP is necessary and not sufficient. 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: curl and the browser both show the VPN IPv4 address. WebRTC still shows the LAN address. You would have called it a pass from this page alone. The pass is the suite, and this command is only the terminal IP line of that suite.
After you finish VPN Leak Test with Curl, open the RookCheck leak suite for WebRTC, DNS, and IPv6 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.
No. WebRTC leaks occur in the browser. Use RookCheck's WebRTC leak test after curl confirms your HTTP exit IP.
No. It is the terminal IP.
Browser WebRTC, DNS resolver identity, and IPv6.
The one that requests the RookCheck IP endpoint and prints the body.