Skip to main content
All Tools

WebRTC Network Diagnostic

Test WebRTC in your browser and find out whether peer-to-peer connections will work on your network. This WebRTC connection test checks STUN server reachability, gathers ICE candidates and detects your NAT type, then estimates how likely a direct connection is. It's a quick diagnostic that runs locally, with no install and no second device.

How to test WebRTC on your network

  1. Click Run Diagnostic. It usually finishes in a few seconds and doesn't ask for your camera or microphone.
  2. Read the NAT type and P2P success estimate first. If it says Open or Moderate, you're probably fine and can stop here.
  3. If it says Strict or Blocked, or connections still fail, move on to a full diagnostic: the connectivity check for browser support, the TURN server tester to confirm a relay works, and the P2P speed test to measure a real connection between two devices.

This page is the quick check. It only sees your side of the connection, so it predicts rather than proves. The step-by-step guide to testing WebRTC connections covers the rest, including chrome://webrtc-internals.

What the results mean

STUN Server Latency shows whether your browser can reach each public STUN server and how long it took. One failure is normal. All four failing usually means a firewall is blocking outbound UDP.

ICE Candidates are the addresses your browser found. host candidates are your local interfaces (like 192.168.x.x). srflx (server reflexive) is your public IP as a STUN server sees it, and its presence means hole-punching is possible. relay candidates come from a TURN server and work through any NAT, at the cost of extra latency. WebRTC tries them in that order and picks the fastest path that works for both peers.

The NAT type comes from comparing those candidates:

  • Open: no NAT detected. Direct connections work freely, around 98% of the time.
  • Moderate: full-cone or restricted-cone NAT, where STUN is enough to punch through. Most home routers land here, with around 85% direct success.
  • Strict (Symmetric): each outbound connection gets a different public port, so hole-punching rarely works (around 15%). Common on corporate and mobile networks.
  • Blocked: no usable candidates at all. Something is stopping UDP entirely, and a TURN relay over TCP or TLS is the likely way through.

Needs Relay is Yes for Strict and Blocked. A connection involves two NATs, though: if the other person is on an Open network, a Strict NAT on your side can still connect directly.

WebRTC diagnostic FAQ

How do I test WebRTC in my browser?

Click Run Diagnostic on this page. It checks four public STUN servers, gathers ICE candidates and works out your NAT type, all inside your browser with nothing to install. To test a full connection between two devices, follow up with the WebRTC speed test.

Does this WebRTC connection test need a second device?

No. The diagnostic only looks at your side of the connection: which addresses your browser can discover and how your router maps them. That's usually enough to predict whether peer-to-peer will work. The speed test is the one that needs two devices.

When do I need a TURN relay?

When a direct connection fails. That typically happens when both peers sit behind symmetric NATs, or when a corporate firewall blocks UDP. TURN adds roughly 50-100ms of latency because all traffic goes through a server, but it gets you connected. SpectrShare falls back to TURN automatically.

Why does the diagnostic show no srflx candidates?

Your browser couldn't get a public address from any STUN server. Either a firewall is blocking outbound UDP, or every STUN server timed out. Without srflx candidates, direct connections across the internet won't work and you'll need a TURN relay.

Is my IP address sent anywhere?

Only to the STUN and TURN servers your browser contacts during the test, which is how STUN works. The diagnostic runs in your browser and the results stay on this page.

Related tools: TURN server tester, P2P speed test, SpectrShare connectivity check