Port 8883 SECURE-MQTT
Port 8883 is the IANA-assigned secure-mqtt port for Secure MQTT (TCP / UDP).
What is port 8883 used for?
Port 8883 is assigned to secure-mqtt and uses TCP / UDP. The IANA registry describes the service as “Secure MQTT”. 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.
Ports are the transport-layer address a service listens on. A client that wants to reach secure-mqtt connects to port 8883. A TCP connection is refused when nothing is listening, while a UDP request simply goes unanswered. That is why a port conflict appears whenever two processes try to bind the same number.
Use the commands below to confirm whether port 8883 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.
Browse all Message queues and streaming ports
Source: IANA Service Name and Transport Protocol Port Number Registry. Registered assignee: [OASIS].
Check and block port 8883
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 = :8883'
sudo ss -ulpn 'sport = :8883'Check on Windows
Get-NetTCPConnection -LocalPort 8883 -State Listen -ErrorAction SilentlyContinue
Get-NetUDPEndpoint -LocalPort 8883 -ErrorAction SilentlyContinueBlock with UFW
sudo ufw deny 8883/tcp
sudo ufw deny 8883/udpBlock with iptables
sudo iptables -A INPUT -p tcp --dport 8883 -j DROP
sudo iptables -A INPUT -p udp --dport 8883 -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 8883 safe to expose?
MQTT over TLS protects traffic in transit, but a broker that allows anonymous clients still permits unauthorised publish and subscribe. Require client authentication. Expose this port only when the service is actually needed. Keep it patched, prefer an encrypted alternative, and limit source addresses with a firewall allowlist.
Where port 8883 is usually used
Most traffic on port 8883 falls into these scenarios. The demo below is a safe way to confirm the listener before you change anything.
- Producers publishing events and consumers subscribing to topics or queues.
- Microservices decoupling background work through a broker on port 8883.
- Local development brokers running in Docker with a published port.
Probe the broker
A TCP probe confirms the listener before you chase authentication or topic errors.
nc -vz 127.0.0.1 8883Common problems with port 8883
Connection refused or timed out
Refused usually means the host is reachable but nothing is listening on port 8883. 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 = :8883' or sudo lsof -i :8883. 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 8883 at a glance
| Port number | 8883 |
|---|---|
| Service name | secure-mqtt |
| Transport protocol | TCP / UDP |
| Category | Message queues and streaming |
| Range | Registered port (1024–10000) |
| Risk level | Medium |
| Registered assignee | [OASIS] |
| Registry description | Secure MQTT |
| Source | IANA Service Name and Transport Protocol Port Number Registry |
Frequently asked questions
What is port 8883 used for?
Port 8883 (SECURE-MQTT) uses TCP / UDP. Secure MQTT.
How do I check if port 8883 is open?
On Linux run `sudo ss -tlpn 'sport = :8883'` and `sudo ss -ulpn 'sport = :8883'`. On Windows run `Get-NetTCPConnection -LocalPort 8883 -State Listen -ErrorAction SilentlyContinue` and `Get-NetUDPEndpoint -LocalPort 8883 -ErrorAction SilentlyContinue` in PowerShell. If the port is open, the output shows a process listening on port 8883; empty output usually means nothing is bound to it.
How do I block port 8883?
With UFW run `sudo ufw deny 8883/tcp` and `sudo ufw deny 8883/udp`. With iptables run `sudo iptables -A INPUT -p tcp --dport 8883 -j DROP` and `sudo iptables -A INPUT -p udp --dport 8883 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot.
Is port 8883 safe to expose?
MQTT over TLS protects traffic in transit, but a broker that allows anonymous clients still permits unauthorised publish and subscribe. Require client authentication. Nevertheless, expose this port only when the service is actually needed. Keep it patched, prefer an encrypted alternative, and limit source addresses with a firewall allowlist.
Related ports
Primary data: IANA Service Name and Transport Protocol Port Number Registry.
Last reviewed 2026-10-30 · Methodology · About · Privacy