Port 5349: TURN-TLS
Port 5349 is STUN and TURN encrypted with TLS, used by WebRTC applications on networks that block plain UDP traffic. Wrapping the connection in TLS lets it travel over the same paths as ordinary encrypted web traffic.
| Port number | 5349 |
|---|---|
| Service | STUN/TURN over TLS |
| Protocol | TCP |
| Category | Proxy & tunneling |
| Default encryption | Yes (TLS/SSH) |
How do I check whether port 5349 is open?
Port 5349 carries TCP, so a connection either completes its handshake or it does not, which makes the check definitive.
| Question | Command | What to know |
|---|---|---|
| Is it open on a remote host? | nc -vz example.com 5349 | A TCP handshake either completes or it does not, so netcat gives a definitive answer in one line. |
| Same check on Windows | Test-NetConnection example.com -Port 5349 | Built into PowerShell. TcpTestSucceeded in the output is the answer; telnet is not installed by default on modern Windows. |
| What is listening locally? | ss -tlnp | grep ':5349 ' | Lists the process bound to port 5349 on Linux. On macOS use lsof -nP -iTCP:5349 -sTCP:LISTEN, on Windows netstat -ano | findstr :5349 |
Replace example.com with the host you are testing. A blocked port and a port with nothing listening on it look identical from the outside, so if a service should be running, check locally before blaming the firewall.
Frequently asked questions
What is port 5349 used for?
Port 5349 is STUN and TURN encrypted with TLS, used by WebRTC applications on networks that block plain UDP traffic. Wrapping the connection in TLS lets it travel over the same paths as ordinary encrypted web traffic.
Is port 5349 TCP or UDP?
Port 5349 (TURN-TLS) uses TCP.
Is port 5349 secure?
Yes. Port 5349 carries encrypted traffic by default, so data in transit is protected.
Should I open port 5349 on my firewall?
Only if you specifically need TURN-TLS. Expose it to the smallest set of trusted sources, and never open database or Windows-service ports to the whole internet.