| Port | 554 |
|---|---|
| Transport | TCP |
| Service | RTSP — Streaming control (IP cameras) |
| Category | Media streaming |
| Range | well-known (0–1023, needs root to bind on Unix) |
| Encrypted | No, plaintext |
| Exposure | Private network or VPN only |
Port 554 RTSP · TCP
RTSP: the control protocol for streaming video, used by nearly every IP camera, NVR and many media servers.
What runs on port 554
RTSP: the control protocol for streaming video, used by nearly every IP camera, NVR and many media servers. The video itself goes over RTP, often on dynamic UDP ports, or interleaved in the RTSP TCP connection. Cameras with default credentials on 554 are a large share of the devices in IoT botnets.
Software that uses it: IP cameras (Hikvision, Dahua, Axis…) · VLC and ffmpeg (clients) · Frigate, ZoneMinder, Shinobi · MediaMTX · GStreamer
Should port 554 be open?
Private network or VPN only. Nothing good comes from this port being reachable from the internet. Keep it on an internal network, reach it over a VPN or an SSH tunnel, and firewall it from everything that does not need it.
- ffprobe rtsp://user:pass@camera:554/stream tells you what the camera offers.
- Never port-forward cameras; put them on a VLAN and view them through the NVR or a VPN.
Check port 554
# on the host: is anything listening, and which process? ss -ltnp 'sport = :554' sudo lsof -i :554 # from another machine: is it reachable? nc -zv host 554 nmap -p 554 host curl -v telnet://host:554 # raw TCP connect test, Ctrl-C to leave
A port that answers from the internet when it should not is the finding; nmap from a machine outside your network (or a VPS) is the honest test, because scans from inside the LAN pass the firewall you are trying to verify.
Allow or block port 554
# ufw (Ubuntu/Debian) sudo ufw allow from 10.0.0.0/8 to any port 554 proto tcp sudo ufw deny 554/tcp # nftables nft add rule inet filter input ip saddr 10.0.0.0/8 tcp dport 554 accept nft add rule inet filter input tcp dport 554 drop # iptables (legacy) iptables -A INPUT -p tcp --dport 554 -s 10.0.0.0/8 -j ACCEPT iptables -A INPUT -p tcp --dport 554 -j DROP # firewalld sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=554 protocol=tcp accept'
Replace 10.0.0.0/8 with the networks that need access. Allowing by source address is the rule that matters; "allow 554" with no source is just "open".
Related ports
Part of the port number reference. Ports are 16-bit numbers; see also the subnet calculator and the packet decoder, which shows ports inside TCP and UDP headers.
Questions
Is port 554 TCP or UDP?
TCP. RTSP is a connection-oriented protocol; there is no UDP service on 554 by default (a scanner reporting UDP 554 open is usually seeing a filtered port).
Is port 554 encrypted?
No, plaintext. Anything sent over it can be read by whoever is on the path, so it belongs on a trusted network or inside a VPN or SSH tunnel.
How do I check whether port 554 is open?
On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 554 and which process. From another machine, nc -zv host 554 or nmap -p 554 host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).
Can RTSP run on a different port?
Yes; the number is a convention, not a requirement. Changing it reduces log noise from scanners but does not add security, and every client, firewall rule and monitoring check then needs the new number. Keep the default unless you have a concrete reason.