TURN Server Test
Test a TURN server online with URL, username and credential. Verify relay ICE candidate allocation and troubleshoot WebRTC TURN connectivity in your browser.
TURN server configuration
Use your own TURN service. This checks relay candidate allocation, not end-to-end relay traffic.
What this TURN server test verifies
This tool creates a WebRTC peer connection in your browser using the TURN URL, username and credential you provide. The test gathers ICE candidates and looks specifically for a relay candidate. A relay candidate is the clearest browser-side sign that the TURN server accepted the configuration and allocated a relay path.
Why TURN matters for WebRTC
Direct peer-to-peer connectivity is not always possible. Corporate firewalls, restrictive NAT behavior and network policy can prevent peers from reaching one another even when STUN discovery succeeds. TURN provides a fallback by relaying traffic through a server. That is why production WebRTC services should test relay behavior instead of assuming a working STUN path is enough.
How to troubleshoot a failed TURN test
First verify the URI format and credentials. Then check whether your TURN service supports the transport you expect, such as UDP, TCP or TLS. Server firewall rules and public port mappings can also prevent allocation. Compare the result with the STUN server test and the broader ICE candidate test to isolate whether the problem is discovery or relay-specific.
For a user-facing readiness check that also validates camera and microphone access, run the main WebRTC test. Credentials entered on this page are used for the live browser test and are not intentionally stored by this version.
TURN server test FAQ
What proves that my TURN server is working?
The key browser-side signal is a relay ICE candidate. It indicates that the browser successfully obtained a relayed candidate using the supplied TURN configuration.
Are my TURN credentials stored?
The current tool uses the credentials in your browser for the live test and does not intentionally persist them.
Why can STUN work while TURN fails?
TURN requires authentication and relay allocation in addition to network reachability, so invalid credentials, firewall rules, transport configuration or server policy can still cause failure.