ProtoStackv0.1

Interactive Protocol Visualizer

Back to all protocols
IGMPRIP
Network & CoreCore trackBeginnerOSI: Application LayerDefault Port: 5353Standard: RFC 6762

mDNS

— Multicast Domain Name System

Multicast DNS reuses the DNS message format and record types but sends queries to the multicast group 224.0.0.251 and to ff02::fb on port 5353. Every device acts as its own authoritative name server for names ending in .local, which is why printers, speakers and laptops can be discovered on a network with no configuration.

Read first: DNS, UDPContent reviewed 2026-11-18

Interactive Session: How mDNS Works

Step through the packet exchange sequence between nodes.

Interactive Execution Sandbox

Interact with a live or clearly-labelled simulated instance of mDNS.

Threat Model & Attack Simulation

How this protocol is attacked in practice, what defenders can see, and which control stops it.

Threat model & attack simulation

Simulated

Defensive education. Every step runs in this page; no traffic is generated or sent.

Attack library

mDNS answer spoofing

Spoofing

A forged multicast answer maps a local service name to the attacker address.

Attackersimulated
mDNStarget
Attack step 1 of 3
Observe a query

The attacker watches multicast traffic for a printer or service discovery request.

What a defender can see

Unusual hosts answering service discovery.

Impact if unmitigated

Service impersonation and possible credential capture.

Defences that matter
  • Segment untrusted devices
  • Filter mDNS at network boundaries
  • Verify service identities where the application supports it

This is a conceptual model for defenders, not an exploit toolkit. It contains no payloads, tooling or instructions for attacking systems you do not own.

Protocol Specification & Architecture

Key characteristics, real-world deployment patterns, and trade-offs.

Core Technical Features

  • DNS wire format with the same record types (A, AAAA, PTR, SRV, TXT)
  • Queries and responses sent to 224.0.0.251 and ff02::fb on UDP 5353
  • Probing and announcing to detect and defend name conflicts
  • Cache-flush bit and a default TTL of 120 seconds for host records
  • Often paired with DNS-SD for service instance discovery

Real-World Use Cases

  • Zero-configuration discovery of printers and file shares
  • AirPlay, Chromecast and smart home device discovery
  • Resolving hostname.local on a home or lab network

Advantages & Strengths

  • No server, no configuration and no DHCP option required
  • Works across operating systems and is built into most platforms

Limitations & Vulnerabilities

  • Traffic stays on the local link and does not cross routers
  • Chatty on large networks and reveals device names to the segment