Run curl commands online with live responses, or copy ready-made examples to check your public IP and debug HTTP — no local install required.
See the IP websites observe. Compare with and without VPN connected.
curl -s https://rookvpn.com/check/api/ip/addressTest APIs, inspect headers, and verify VPN exit IPs from any machine — including locked-down browsers and Chromebooks.
Run Curl Online exists to run an HTTP request from the browser UI when the machine has no curl installed, and compare that result with a real curl on a machine that does. 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 Run Curl Online in order. 1. Pick a template or paste a URL. 2. Run it and read status, headers, and body. 3. If you are checking a VPN, compare with the IP page on RookCheck. 4. Do not paste production tokens into a shared screen. 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.
The request is executed server-side so locked-down browsers can still see a response. That means the URL is sent to RookCurl, unlike the hash tools. This is not a tunnel for arbitrary TCP. Private network addresses are blocked. 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: a Chromebook with no shell uses the page to GET https://rookvpn.com/check/api/ip/address and reads the exit IP. A laptop on the same VPN runs the same URL in real curl. The addresses should match. If they do not, the browser and the terminal are not on the same route. The online tool is the browser path, not a hidden local socket.
After you finish Run Curl Online, open the bearer-token example when the API needs an Authorization header 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 Run Curl Online for one job: to run an HTTP request from the browser UI when the machine has no curl installed, and compare that result with a real curl on a machine that does. Bring the before-and-after evidence with you if you change a setting. A VPN icon, a decoded token, a generated password, or a stripped file is not finished until you have checked the output the way this page describes. Then follow the related guide for the long version, and the sibling tool only when the next job is actually different. Keep secrets out of the same message as the link or the file that needs them. If a second run does not match the first, stop and find what changed instead of publishing the first result.
Example: a Chromebook with no shell uses the page to GET https://rookvpn.com/check/api/ip/address and reads the exit IP. A laptop on the same VPN runs the same URL in real curl. The addresses should match. If they do not, the browser and the terminal are not on the same route. The online tool is the browser path, not a hidden local socket. Work the page in this order: Pick a template or paste a URL. Run it and read status, headers, and body. If you are checking a VPN, compare with the IP page on RookCheck. Do not paste production tokens into a shared screen. Limits that still apply after a clean result: The request is executed server-side so locked-down browsers can still see a response. That means the URL is sent to RookCurl, unlike the hash tools. This is not a tunnel for arbitrary TCP. Private network addresses are blocked.
Paste or pick a template on rookvpn.com/curl, then execute. RookCurl runs the request from the server and shows status, headers, and body — no local curl install needed.
Yes. Basic curl execution on rookvpn.com/curl needs no account.
Yes — use the built-in examples or paste curl -s https://rookvpn.com/check/api/ip/address.
No. It runs the request for you and shows the response.
Treat the box like a shared terminal. Use a test token, not a long-lived production secret, if the screen can be seen.
No. Local and private addresses are rejected.