Acerca de WebRTC Diagnostics
Check browser WebRTC, ICE candidates, STUN, and TURN
Check browser WebRTC, ICE candidates, STUN, and TURN The interface is designed to keep the important input, options, and result close together so you can finish a small development task without leaving your browser.
Cómo usar esta herramienta de desarrollo
- Open the tool and confirm that your browser exposes RTCPeerConnection and RTCDataChannel.
- Add one or more STUN or TURN servers. TURN checks require the username and credential supplied by that server.
- Run the STUN/TURN check to see whether each service returns the candidate type it is expected to provide.
- Run the candidates check to inspect host, server-reflexive, peer-reflexive, relay, and mDNS-hidden candidates from this browser.
Privacidad y tratamiento de datos
The checks run in your current browser. STUN and TURN addresses, credentials, and candidate traffic go directly to the servers you configure; this site does not receive or store them. The configuration is saved only in this browser so you can reuse it on the next visit.
Herramientas de desarrollo relacionadas
Preguntas frecuentes
Does this tool require a second browser?
No. The diagnostic suite checks browser support, ICE candidate gathering, and individual STUN/TURN service responses without creating a peer-to-peer session with another device.
Why does a STUN check need a srflx candidate?
A server-reflexive candidate shows that the STUN service returned the public address mapping needed for NAT traversal. A local host candidate alone does not prove that STUN answered.
Why does TURN need credentials?
TURN relays normally require authentication. The checker treats a relay candidate as success only when the server returns one using the credentials you supplied.