mDNS, SSDP and UPnP: how LAN service-discovery protocols leak device info
mDNS, SSDP and UPnP let devices on a local network find each other automatically, and all three work by broadcasting information — device names, models, available services — to anything listening on the same network segment, which is convenient on a trusted home LAN and a quiet information leak on any network an attacker can reach. AdminKit explains the risk.
By AdminKit team, Netbase JSC · Updated
Key takeaways
- mDNS, DNS-SD and SSDP let devices find each other with no setup, by announcing names, services and often software versions to everyone on the local network.
- On a trusted home LAN that’s a fair trade; on shared office, hotel or coworking networks it’s free reconnaissance for anyone else connected.
- UPnP’s port-forwarding feature is the serious risk: any device inside, including malware, can ask the router to open a port to the internet.
- Disable UPnP unless something specific needs it, keep discovery-heavy devices on their own segment, and check your router’s mapping table.
Why does “zero configuration” networking leak information?
mDNS, SSDP and UPnP all trade a small amount of information exposure for the convenience of devices finding each other automatically. That tradeoff made sense when these protocols were designed for small, implicitly trusted home networks — the same assumption baked into a lot of consumer IoT and home-network design from that era. RFC 6762 (also on the IETF Datatracker), which defines multicast DNS (mDNS), is explicit that it’s meant for “networks where no conventional DNS server is available,” a description that fits a home LAN but not a shared office Wi-Fi network, a hotel network, or a coworking space where dozens of unrelated devices sit on the same segment. On any of those less-trusted networks, the same broadcasts that let your laptop find a printer also let every other device on that network see your laptop’s hostname, and often its operating system fingerprint and the services it’s running.
SSDP works similarly for service announcements: a smart TV, NAS, or IoT hub periodically announces itself and its capabilities to the local multicast group, which is how your phone’s casting app finds a Chromecast without you typing in an IP address. DNS-SD (RFC 6763) layers the same idea on top of mDNS using SRV, PTR and TXT records, which is how a printer or media server advertises its name, port and capabilities for discovery without any central directory. The same announcement tells anyone else listening exactly what that device is and often its software version — useful reconnaissance information for an attacker already on the network, with zero effort required to obtain it.
The three protocols work at different layers, but all of them stay on the local network segment by design:
| Protocol | Transport | Where it sends | What it reveals | Defined in |
|---|---|---|---|---|
| mDNS | UDP 5353 | 224.0.0.251 / ff02::fb | Hostnames ending in .local, device addresses | RFC 6762 |
| DNS-SD | Runs over mDNS | Same as mDNS | Service types, ports, TXT details such as model names | RFC 6763 |
| SSDP | UDP 1900 | 239.255.255.250 | Device type, a description URL, a SERVER header with OS and product versions | UPnP Device Architecture |
| UPnP IGD | HTTP to the router | Unicast, inside the LAN | Nothing by itself; lets devices create port forwards | UPnP IGD service specs |
How do you see what your own devices announce?
The quickest way to understand the exposure is to look at it from your own laptop on your own network. On Linux with Avahi installed, avahi-browse lists every service advertised over mDNS/DNS-SD; on macOS, dns-sd -B does the same for one service type. The output below is an example of the kind of entries a home network shows:
$ avahi-browse -at
+ wlan0 IPv4 Office Printer Internet Printer local
+ wlan0 IPv4 living-room-tv _googlecast._tcp local
+ wlan0 IPv4 nas-backup Microsoft Windows Network local
+ wlan0 IPv4 nas-backup SSH Remote Terminal local
Every line is visible to any other device on the same segment, with no login. Names like nas-backup also tell a visitor which machine is worth a closer look.
SSDP discovery is an HTTP-style message sent to the multicast group. Per the UPnP Device Architecture, a control point searching for everything sends:
M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
MAN: "ssdp:discover"
MX: 2
ST: ssdp:all
Each device answers with a LOCATION URL pointing at its XML description (manufacturer, model, serial number on many devices) and a SERVER header naming its operating system and UPnP stack versions. That’s useful to a casting app, and equally useful to anyone checking which devices run outdated firmware.
Why is UPnP port forwarding the real risk?
Discovery alone is a privacy and fingerprinting concern. UPnP’s Internet Gateway Device (IGD) extension is a different category of risk, because it doesn’t just announce information — it lets a device on the network actively request that the router set up a port forward from the public internet to that device, with no authentication beyond “the request came from inside the network.” This exists for legitimate reasons (game consoles needing inbound connectivity, VoIP clients negotiating calls, some video conferencing software), related to the kind of NAT traversal behavior described in RFC 6886. But a router generally has no way to tell a legitimate device’s request from a request made by malware already running on a compromised device inside the network — and that’s exactly the exposure pattern CISA’s advisories on UPnP-related vulnerabilities have documented repeatedly: a device inside the network silently opens a port to the public internet, with no indication visible to the person using the network unless they go looking at the router’s mapping table.
Most routers show that table under a UPnP or NAT section of the admin panel. Entries look roughly like this (example values):
| External port | Protocol | Internal address | Internal port | Description |
|---|---|---|---|---|
| 3074 | UDP | 192.168.1.40 | 3074 | Game console |
| 8443 | TCP | 192.168.1.73 | 443 | Camera remote access |
| 23 | TCP | 192.168.1.73 | 23 | (no description) |
Every row is a port open to the internet. Check that each one maps to a device you recognise and a feature you use; a mapping for an admin or Telnet port, or one with no description pointing at an IoT device, is a reason to unplug that device and investigate before anything else.
UPnP isn’t the only way a device can ask for a mapping. RFC 6886 defines NAT Port Mapping Protocol (NAT-PMP), which serves the same purpose and is supported by some routers alongside or instead of UPnP IGD. When you switch UPnP off, look for a separate NAT-PMP setting on the same page and turn it off too, unless something you rely on needs it; otherwise devices that speak NAT-PMP can keep opening ports as before.
How risky is discovery on your network?
- Lowest risk: mDNS/SSDP on a genuinely trusted, small home LAN. The convenience generally outweighs the exposure if the only other devices on the network are also yours.
- Meaningful risk: mDNS/SSDP on any shared or semi-trusted network. Office networks with guest access, coworking spaces, or any LAN segment shared with devices you don’t control turns passive discovery into free reconnaissance for anyone else on that segment. On a genuinely hostile shared segment, that reconnaissance is often paired with more active attacks like ARP spoofing, which can intercept traffic outright rather than just observe what’s broadcast.
- Highest risk: UPnP’s automatic port-forwarding, anywhere. This is the one feature of the three that can turn an internal issue (a compromised IoT device or piece of malware) into an internet-facing one, without any user action or awareness.
What should you do about it?
- Segment discovery-heavy devices onto their own network. Keep IoT devices, smart TVs, and anything relying on mDNS/SSDP discovery off the same network segment as work laptops or anything handling sensitive data — this is the same segmentation principle covered in our guide on IPv6 home devices needing a firewall.
- Disable UPnP on your router unless you have a specific, understood need for it. Most consumer and small-office routers expose this as a simple on/off toggle in the admin panel; check the router’s active UPnP mapping list first to see what, if anything, currently relies on it before disabling.
- Don’t expose mDNS/SSDP/UPnP traffic across network boundaries. These protocols are meant to stay on a single local segment; a router or firewall that accidentally forwards multicast traffic between a guest network and a trusted one, or between VLANs, defeats the segmentation that limits their exposure.
- Check what’s actually reachable from outside. AdminKit’s port check tool scans a fixed list of nine commonly-misconfigured TCP ports against your own public IP — useful for confirming whether UPnP opened one of those specific ports on your behalf without your direct action. For a port outside that list, check your router’s own UPnP mapping table directly, or test it manually from outside your network.
Does turning off discovery break anything?
Usually less than people expect, but it’s worth knowing what depends on what before changing settings:
- Disabling UPnP on the router can affect online multiplayer on game consoles and some peer-to-peer or VoIP apps that need inbound connections. If one of these stops working, add a single manual port forward for that device instead of re-enabling UPnP for everything.
- Blocking mDNS/SSDP between network segments means a phone on the main Wi-Fi won’t find a printer or TV on the IoT segment by itself. Some routers offer a controlled mDNS relay for just the service types you choose; otherwise, connect to those devices by their IP address.
- Turning discovery off on a laptop that travels has little downside: on hotel or coworking Wi-Fi you rarely need to find anyone else’s devices, and your own laptop stops announcing itself to strangers.
Related checks
These discovery protocols are one layer of a broader “what does my network expose by default” question that also covers IoT device segmentation and open management ports; see our guides on IPv6 home devices needing a firewall and is port 1883 (MQTT) open for related angles on the same theme.
This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.
Frequently asked questions
What's the difference between mDNS, SSDP and UPnP?
mDNS (multicast DNS, RFC 6762) is a name-resolution protocol — it lets devices answer 'who has the name printer.local?' without a central DNS server, and is the basis for Apple's Bonjour/AirPlay discovery. SSDP (Simple Service Discovery Protocol) is how devices on a network announce and discover available services, commonly used by smart TVs, media servers and IoT hubs. UPnP (Universal Plug and Play) is a broader framework that uses SSDP for discovery but adds the ability for a device to actually request that a router automatically open a port on its behalf — the piece with the most serious security implications of the three.
What information does mDNS/SSDP actually broadcast?
Typically the device's hostname, model or manufacturer string, the services it offers (printing, file sharing, media streaming, a specific IoT vendor's API), and sometimes software version information — all sent unauthenticated to anyone passively listening on the same network segment. None of this requires compromising the device; it's broadcast by design so other devices can discover it, which means anyone else on the same Wi-Fi network or LAN segment receives the same broadcasts for free.
Why is UPnP's port-opening feature considered risky?
UPnP's Internet Gateway Device (IGD) protocol lets any device on the local network ask the router to open a specific port and forward it to that device — originally meant to simplify things like game consoles or VoIP software asking for inbound connectivity without a human configuring port forwarding manually. The security problem is that the router generally can't distinguish a legitimate request from one made by malware already running on a compromised device inside the network; several public research disclosures over the years have documented UPnP implementations opening ports to the internet without any user awareness or consent, turning an internal compromise into internet-facing exposure.
Should I just disable mDNS, SSDP and UPnP everywhere?
Not necessarily everywhere — mDNS and SSDP enable real, expected functionality (AirPlay, Chromecast discovery, network printing, media server discovery) that many households and offices rely on, and disabling them can break those features. The actual fix is scoping where they're reachable from: these protocols should never cross from a trusted LAN segment to a guest network, and router-level UPnP should be disabled unless you have a specific, understood reason to need automatic port forwarding — most home and office setups function fine without it.
How do I check if these protocols are exposing my network to the internet?
The main risk isn't usually these protocols leaking across the public internet directly — multicast traffic doesn't normally route off the local segment — it's UPnP-opened ports ending up reachable from outside. Use AdminKit's my IP tool to confirm your public-facing address, and check your router's own port-forwarding or UPnP mapping list (most consumer router admin panels show currently active UPnP-opened ports) for any forwarding rule you didn't set up manually.
Sources
- RFC 6762 — Multicast DNS
- RFC 6886 — NAT Port Mapping Protocol (related UPnP IGD port-forwarding background)
- CISA — Alert on UPnP-related vulnerabilities and exposure
- RFC 6762 — IETF Datatracker document record
- RFC 6763 — DNS-Based Service Discovery
- Open Connectivity Foundation — UPnP Device Architecture 2.0 (SSDP discovery)
Want AdminKit to watch this for you?
Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.
Talk to an expert
Huy Nguyen (David), Founder & CEO, Netbase JSC
Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.