Port 1883 — MQTT
TCP registered
What runs on port 1883
Lightweight publish/subscribe messaging for IoT devices.
Security considerations
Unencrypted and often unauthenticated by default. Use port 8883 for MQTT over TLS.
Checking whether something is listening
# Linux / macOS — what is bound to the port
sudo lsof -i :1883
sudo ss -lntp | grep :1883
# Windows
netstat -ano | findstr :1883
Get-NetTCPConnection -LocalPort 1883
# is it reachable from outside?
nc -zv example.com 1883
curl -v telnet://example.com:1883
Freeing the port
# find the process, then stop it
sudo lsof -ti :1883 | xargs kill # Linux / macOS
netstat -ano | findstr :1883 # note the PID, then:
taskkill /PID <pid> /F # Windows
Should this port be open to the internet?
Usually not. Expose it only if a specific external client needs it, and restrict by source address where you can.
Quick reference
| Port | 1883 |
| Protocol | TCP |
| Service | MQTT |
| Range | Registered (1024–49151) — any user process may bind |
Frequently asked questions
What is port 1883 used for?
Lightweight publish/subscribe messaging for IoT devices.
Is it safe to open port 1883?
Unencrypted and often unauthenticated by default. Use port 8883 for MQTT over TLS.
How do I check if port 1883 is open?
Locally, sudo lsof -i :1883 on macOS or Linux, or netstat -ano | findstr :1883 on Windows. From outside, nc -zv host 1883 tells you whether anything answers.
Why do I get "address already in use" on port 1883?
Another process is bound to it — often a previous run of your own program that did not exit cleanly. Find it with lsof -ti :1883 and stop it, or configure your application to use a different port.
Can I change the port this service uses?
Almost always yes, in the service's configuration. Moving off a default port reduces automated scan noise, but it is obfuscation rather than security — a real attacker scans all 65,535.