Port 5349 STUNS
Port 5349 is the IANA-assigned stuns port for Session Traversal Utilities for NAT (STUN) port (TCP).
What is port 5349 used for?
Port 5349 is assigned to stuns and uses TCP. The IANA registry describes the service as “Session Traversal Utilities for NAT (STUN) port”. It sits in the registered range, the block used by databases, application servers and developer tooling. Port conflicts here are common when several local services start at once. The same port is also registered under stun-behaviors.
Ports are the transport-layer address a service listens on. A client that wants to reach stuns connects to port 5349. If nothing is listening, the connection is refused. That is why a port conflict appears whenever two processes try to bind the same number.
Use the commands below to confirm whether port 5349 is actually in use before you change firewall rules. Blocking the port stops new inbound traffic at the firewall, but it does not stop a local process from listening, and it does not remove the service from the machine.
Source: IANA Service Name and Transport Protocol Port Number Registry. Registered assignee: [IESG]. Reference: [RFC 8489].
Check and block port 5349
Copy-ready commands for the protocols assigned to this port. Run the check first, then block only what should not be reachable.
Check on Linux
sudo ss -tlpn 'sport = :5349'Check on Windows
Get-NetTCPConnection -LocalPort 5349 -State Listen -ErrorAction SilentlyContinueBlock with UFW
sudo ufw deny 5349/tcpBlock with iptables
sudo iptables -A INPUT -p tcp --dport 5349 -j DROPThese commands are examples for a typical host. Check the listener before you change firewall rules, and persist iptables rules with iptables-save or netfilter-persistent. On Windows, use Windows Defender Firewall or New-NetFirewallRule for persistent blocks. The iptables rules here cover IPv4; mirror them with ip6tables if IPv6 is enabled.
Is port 5349 safe to expose?
This port is not on our curated list of services with a widely exploited profile. Exposure is only safe when the listening service is intended, patched and protected by a firewall. Keep the listening service patched and remove it if unused. A default-deny firewall policy with explicit allow rules is still the safest baseline.
Where port 5349 is usually used
Most traffic on port 5349 falls into these scenarios. The demo below is a safe way to confirm the listener before you change anything.
- Application backends and supporting services that use a fixed registered number.
- Containers or local stacks that publish the port on the host.
- Firewall and exposure reviews before the service goes to production.
Probe the port
Confirm something is listening before you debug the client. This checks a TCP handshake on the port.
nc -vz 127.0.0.1 5349Common problems with port 5349
Connection refused or timed out
Refused usually means the host is reachable but nothing is listening on port 5349. A timeout more often means a firewall drop, a wrong host or a service bound to a different interface.
Port already in use
Find the process holding the port with sudo ss -tlpn 'sport = :5349' or sudo lsof -i :5349. Stop that process or configure it to bind another port; killing it without identifying it can take down a production service.
Firewall rule did not survive a reboot
UFW and Windows Firewall keep rules across restarts. Raw iptables rules do not: save them with iptables-save or the netfilter-persistent package, and re-apply after upgrades that reset the ruleset.
The port is blocked but still reachable
A firewall rule filters inbound traffic; it does not close the listener. Confirm with the check command above and bind the service to 127.0.0.1 when only local clients need it.
Port 5349 at a glance
| Port number | 5349 |
|---|---|
| Service name | stuns |
| Aliases | stun-behaviors |
| Transport protocol | TCP |
| Category | Application services |
| Range | Registered port (1024–10000) |
| Risk level | Standard/Low |
| Registered assignee | [IESG] |
| Reference | [RFC 8489] |
| Registry description | Session Traversal Utilities for NAT (STUN) port |
| Source | IANA Service Name and Transport Protocol Port Number Registry |
Frequently asked questions
What is port 5349 used for?
Port 5349 (STUNS) uses TCP. Session Traversal Utilities for NAT (STUN) port.
How do I check if port 5349 is open?
On Linux run `sudo ss -tlpn 'sport = :5349'`. On Windows run `Get-NetTCPConnection -LocalPort 5349 -State Listen -ErrorAction SilentlyContinue` in PowerShell. If the port is open, the output shows a process listening on port 5349; empty output usually means nothing is bound to it.
How do I block port 5349?
With UFW run `sudo ufw deny 5349/tcp`. With iptables run `sudo iptables -A INPUT -p tcp --dport 5349 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot.
Is port 5349 safe to expose?
This port is not on our curated list of services with a widely exploited profile. Exposure is only safe when the listening service is intended, patched and protected by a firewall. Nevertheless, keep the listening service patched and remove it if unused. A default-deny firewall policy with explicit allow rules is still the safest baseline.
Related ports
- Port 5321 · bsfsvr-zn-sslWebservices-based Zn interface of BSF over SSL
- Port 5350 · pcp-multicastPort Control Protocol Multicast
- Port 5318 · pkix-cmcPKIX Certificate Management using CMS (CMC)
- Port 5317 · hpdevmsHP Device Monitor Service
- Port 5364 · kdnetMicrosoft Kernel Debugger
- Port 5316 · hpblademsHPBladeSystem Monitor Service
Primary data: IANA Service Name and Transport Protocol Port Number Registry.
Last reviewed 2026-10-30 · Methodology · About · Privacy