| Port | 1900 |
|---|---|
| Transport | UDP |
| Service | SSDP / UPnP |
| Category | IoT and home automation |
| Range | registered (1024–49151) |
| Encrypted | No, plaintext |
| Exposure | Private network or VPN only |
Port 1900 SSDP / UPnP · UDP
SSDP: the discovery part of UPnP, multicast to 239.255.255.250:1900. Media players, smart TVs, printers, routers and game consoles announce themselves and respond to M-SEARCH.
What runs on port 1900
SSDP: the discovery part of UPnP, multicast to 239.255.255.250:1900. Media players, smart TVs, printers, routers and game consoles announce themselves and respond to M-SEARCH. Routers that answer SSDP on their WAN side are a known reflection/amplification vector and also expose UPnP port-mapping (the "IGD" that lets any LAN device open ports from the outside).
Software that uses it: Windows (SSDP Discovery service) · miniupnpd (routers) · DLNA servers (Plex, Jellyfin, Kodi) · Sonos, Chromecast-era devices
Should port 1900 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.
- Block UDP 1900 inbound on the WAN and consider disabling UPnP on the router.
- gssdp-discover or "nmap -sU -p 1900 --script upnp-info" lists what is announcing.
Check port 1900
# on the host: is anything listening, and which process? ss -lunp 'sport = :1900' sudo lsof -i :1900 # from another machine: is it reachable? nc -zuv host 1900 sudo nmap -sU -p 1900 host
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 1900
# ufw (Ubuntu/Debian) sudo ufw allow from 10.0.0.0/8 to any port 1900 proto udp sudo ufw deny 1900/udp # nftables nft add rule inet filter input ip saddr 10.0.0.0/8 udp dport 1900 accept nft add rule inet filter input udp dport 1900 drop # iptables (legacy) iptables -A INPUT -p udp --dport 1900 -s 10.0.0.0/8 -j ACCEPT iptables -A INPUT -p udp --dport 1900 -j DROP # firewalld sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=1900 protocol=udp accept'
Replace 10.0.0.0/8 with the networks that need access. Allowing by source address is the rule that matters; "allow 1900" 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 1900 TCP or UDP?
UDP. SSDP / UPnP is datagram-based; TCP 1900 is not used by it.
Is port 1900 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 1900 is open?
On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 1900 and which process. From another machine, nc -zv host 1900 -u or nmap -p 1900 -sU host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).
Can SSDP / UPnP 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.