What is WebRTC?
WebRTC (Web Real-Time Communication) is a set of web standards and APIs for real-time audio, video, and data communication in browsers. It is used for meetings, calls, and data exchange. Browsers gather possible network paths through ICE; this tool creates a data channel only and does not request audio or video.
What can WebRTC candidates reveal?
Candidates describe possible connection paths. They may be visible to page scripts or a communication peer during negotiation, depending on the browser, privacy settings, and connection flow. A public candidate may be a VPN exit; private candidates, mDNS hostnames, and public candidates have different meanings.
ICE, STUN, and TURN
ICE gathers and selects connection candidates. STUN helps a client observe the mapped address seen from outside its network. TURN relays traffic when a direct connection is not possible; it is not simply an address lookup service. This tool contacts Cloudflare STUN first, then Google STUN only after a timeout, failure, or no usable public server-reflexive candidate.
How can I investigate a possible path difference?
Check whether your VPN uses a full tunnel and whether split tunneling is enabled. Review the VPN provider's official WebRTC guidance. Update your browser and VPN client, then test again. Before restricting WebRTC, consult documentation for your current browser version; doing so may affect meetings, calls, or other sites.
Limitations
Results depend on the browser, operating system, VPN, extensions, network policy, and STUN reachability. mDNS may hide local addresses; no candidates or a failed request does not mean no leak. Results describe this session only, not every site or connection. The tool does not test Claude connectivity, account status, or platform decisions.
Requests and privacy
Only after you start the test does the browser create a WebRTC data channel and contact Cloudflare STUN first. Google STUN may be contacted only after a timeout, failure, or no usable public candidate. Each STUN service may see the network address making the request. ICE candidates are processed in this page's memory only; they are not sent to the IPVeya API or written to the URL, cookies, or local storage. The page also requests the current egress IP as a local comparison reference. No camera or microphone permission is requested.