Port 5672 — AMQP / RabbitMQ
TCP registered
What runs on port 5672
Message broker protocol.
AMQP, the protocol behind RabbitMQ. This is the message traffic itself; the management web interface is a separate service on 15672 and is the one that ships with a default guest/guest account. That account is restricted to localhost in current versions, but older deployments and hastily written container images frequently expose it, which grants full control of the broker.
Security considerations
The default guest/guest account only works from localhost, but people disable that. Do not.
Checking whether something is listening
# Linux / macOS — what is bound to the port
sudo lsof -i :5672
sudo ss -lntp | grep :5672
# Windows
netstat -ano | findstr :5672
Get-NetTCPConnection -LocalPort 5672
# is it reachable from outside?
nc -zv example.com 5672
curl -v telnet://example.com:5672
Freeing the port
# find the process, then stop it
sudo lsof -ti :5672 | xargs kill # Linux / macOS
netstat -ano | findstr :5672 # 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.
Opening or blocking port 5672
Finding the port is usually the first half of the job. Start narrow — the second rule is there for services that genuinely serve the public, and most do not:
# ufw — Debian, Ubuntu
sudo ufw allow from 10.0.0.0/8 to any port 5672 proto tcp
sudo ufw allow 5672/tcp # only if it genuinely serves the public
# firewalld — RHEL, Fedora, CentOS
sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=5672 protocol=tcp accept'
sudo firewall-cmd --reload
# iptables, if you are still there
sudo iptables -A INPUT -p tcp --dport 5672 -s 10.0.0.0/8 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 5672 -j DROP
# Windows
New-NetFirewallRule -DisplayName "AMQP / RabbitMQ 5672" -Direction Inbound -Protocol TCP -LocalPort 5672 -RemoteAddress 10.0.0.0/8 -Action Allow
10.0.0.0/8 stands in for a private range — substitute your own. Note that a firewall rule does not undo a service bound to 0.0.0.0; it only stops packets reaching it, and a misconfigured or disabled firewall then exposes it immediately.
Quick reference
| Port | 5672 |
| Protocol | TCP |
| Service | AMQP / RabbitMQ |
| Range | Registered (1024–49151) — any user process may bind |
Frequently asked questions
What is port 5672 used for?
Message broker protocol.
Is it safe to open port 5672?
The default guest/guest account only works from localhost, but people disable that. Do not.
How do I check if port 5672 is open?
Locally, sudo lsof -i :5672 on macOS or Linux, or netstat -ano | findstr :5672 on Windows. From outside, nc -zv host 5672 tells you whether anything answers.
Why do I get "address already in use" on port 5672?
Another process is bound to it — often a previous run of your own program that did not exit cleanly. Find it with lsof -ti :5672 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.
Other common ports
- Port 6379 — Redis
- Port 8000 — HTTP alternate
- Port 8080 — HTTP alternate
- Port 8443 — HTTPS alternate
- Port 8883 — MQTT over TLS
- Port 9000 — PHP-FPM / SonarQube / Portainer
- Port 9090 — Prometheus
- Port 9200 — Elasticsearch
- Port 11211 — Memcached
- Port 27017 — MongoDB
- Port 20 — FTP data
- Port 21 — FTP control
- Port 22 — SSH / SFTP
- Port 23 — Telnet
- Port 25 — SMTP
- Port 53 — DNS
- Port 67 — DHCP server
- Port 68 — DHCP client