Port 2535Multicast Address Dynamic Client Allocation Protocol (MADCAP)

MADCAP dynamically allocates multicast addresses to clients, typically over UDP port 2535.

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
2/10

safe

lookups
0

rank 993 of 4,114 · top 24%

also known as madcap, Multicast Address Dynamic Client Allocation Protocol

Technical Details

what runs on :2535

MADCAP uses DHCP-like request and reply messages to allocate, renew, and release multicast addresses. Standard MADCAP exchanges use UDP, with the server listening on port 2535; IANA also lists TCP for the service, but that does not mean ordinary MADCAP deployments use TCP. It is a separate protocol from DHCP despite the similar message model.

Security Information

exposure of :2535

risk score

2/ 10safe

routine exposure. this port is rarely the way in on its own — keep it patched and logged and move on.

network services averages 2.7 across 1,313 ports — this one sits 0.7 below.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

MADCAP is not encrypted by default, and its allocation requests should be treated as control traffic for a trusted multicast network. Avoid exposing it to the public internet: an accessible service may allow unwanted allocation requests or resource exhaustion, while spoofed traffic can interfere with allocation.

the 8 most looked-up other ports in network services — 1,313 ports carry that label.

risk mix of the 8 listed

  • caution100%

0 of 8 encrypted