WebRTC Test

WebRTC Test checks the part of your browser that video calls, voice chat, screen sharing and peer-to-peer file transfers in web apps rely on. It does not just look for WebRTC: it creates two connections inside this page, lets each gather the network addresses (candidates) your device can offer, joins them to each other, opens a data channel and sends twenty messages back and forth. If that works, WebRTC is working in this browser, and the page shows how long the messages took to go round. It then lists every candidate the browser offered — its type, protocol and address — and says what that address is. Most current browsers hide your local network address behind a random “.local” name; the page tells you whether yours does, which is what people mean by a WebRTC leak test.

1. Open the page: the test runs by itself and takes a second or two.
2. Read the message at the top: a green one means WebRTC connected.
3. Look at the table of candidates to see what addresses the browser offers, and whether your local address is hidden.
4. Press Run again after changing a setting, an extension or a VPN.

• Because no STUN or TURN server is used (on purpose), this test cannot show your public IP address or prove that a call across the internet will connect. Calls between networks also depend on firewalls and the call service’s own servers.
• The round-trip time is inside your own device, not across the internet, so it says nothing about your connection’s speed or latency.
• Browsers show more addresses after a page has camera or microphone permission, and some show raw local addresses in normal use. This page has not asked for either, so it shows what an ordinary site would see.
• Some privacy extensions and settings switch WebRTC off entirely or limit it to one network route; then the test fails or shows fewer candidates.
• No server is used — not even the STUN servers that WebRTC normally asks for your public address. Both ends of the connection are inside this page, so nothing leaves your device and your public IP address is never looked up. The candidates are shown only to you.

Older browsers gave any page your device’s real local network address through WebRTC, and with a STUN server your public address too — even behind some VPNs. Current browsers hide the local address behind a random .local name. If the table shows only .local names, your local address is hidden.

If this test passes, WebRTC itself works, and the problem is more likely the network between you and the other person: a strict firewall, a company network, or the call service. If this test fails, an extension or setting is blocking WebRTC — try a private window with extensions off.

It never looks up your public address. It may show a local address (such as 192.168.x.x) if your browser offers it; that address only means something on your own network.

Host is your device’s own address. Server reflexive (srflx) is the public address a STUN server sees, and relay goes through a TURN server. This page uses neither server, so only host candidates appear.