Using the RookCheck Suite

RookCheck bundles browser-based tests to audit IP visibility, VPN leaks, and fingerprinting surface — free at rookvpn.com/check.

RookCheck is the diagnostic hub for RookVPN users and anyone evaluating a VPN provider. Tests run in your browser and call RookVPN APIs where needed; results are designed for actionable pass/fail interpretation.

IP and network tab

• IP Info: Shows the address websites see, ASN, and coarse geolocation.
• Headers: Reflects request headers as seen by the edge — useful for verifying proxy/VPN header injection.
• Timezone: Compares JS timezone with IP geolocation mismatches (common when exiting in another country).

Start here after connecting VPN: the IP should match your exit, not your ISP.

Leak testing tab

• WebRTC: Surfaces STUN-derived candidates. See WebRTC leak fix.
• DNS: Lists resolvers answering your queries. See DNS leak fix.
• IPv6: Highlights v6 addresses reachable outside the tunnel. See IPv6 leak fix.

Run all three after every VPN client update or OS upgrade.

Fingerprinting tab

Canvas, WebGL, and font probes show how unique your browser appears. VPNs do not always hide fingerprinting — use these tools to decide if you need separate browser profiles for sensitive research.

Terminal parity with RookCurl

Scripts and RookCurl can hit the same IP endpoint:

curl -s https://rookvpn.com/check/api/ip/address

Compare curl output with the browser IP card — discrepancies indicate split tunneling or different network paths (Wi‑Fi vs Ethernet).

Share reports

RookCheck can generate shareable report links for support tickets. Redact personal notes before sharing URLs externally.

Related

• VPN leak testing guide
• Check public IP via curl

Check the result

Run the suite in this order: disconnected IP, connected IP, WebRTC, DNS, IPv6. Stop on the first channel that still shows the home network and fix that channel before you collect more screenshots. The leak testing guide is the long form. The suite pages are the measurement.

A VPN icon is not one of the steps. Browser fingerprint pages are a different question. They do not move when the tunnel works, and a working tunnel does not make a canvas hash common.