Port 496PIM Rendezvous Point Discovery
PIM Rendezvous Point Discovery uses TCP and UDP port 496 for multicast routing control-plane discovery.
- transport
- tcp · udp
- in transit
- cleartext
- assignment
- official
- risk
- 4/10
- lookups
- 0
2 transports registered
payload readable on path
registered with iana
caution
rank 993 of 4,830 · top 21%
also known as pim-rp-disc, PIM RP Discovery
Technical Details
what runs on :496PIM-RP-DISC uses UDP port 496 for binary, connectionless control messages; normal operation has no TCP-style handshake or stream framing. Candidate RPs send periodic announcements to the Auto-RP announcement group 224.0.1.39, while mapping agents distribute discovered RP mappings through the discovery group 224.0.1.40. TCP is included in the registry assignment, but ordinary Auto-RP deployments do not use a TCP listener on this port. PIM itself uses IP protocol 103 for other control messages, and Bootstrap Router (BSR) is an alternative RP-discovery mechanism that does not depend on this port.
Security Information
exposure of :496risk score
4/ 10caution
worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.
network services averages 2.7 across 1,426 ports — this one sits 1.3 above.
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
Auto-RP traffic is generally unauthenticated and unencrypted, so an attacker able to inject or interfere with the multicast control traffic could alter RP mappings, disrupt multicast routing, or redirect multicast streams. The port should normally be limited to trusted multicast-routing interfaces and should not be exposed to the public Internet; filtering, multicast-boundary controls, and PIM authentication or a more robust discovery mechanism should be considered where supported.
Related Ports
the 8 most looked-up other ports in network services — 1,426 ports carry that label.
| port | service | risk | |||
|---|---|---|---|---|---|
| :9080 | Groove RPC | TCPUDP | Web Services | caution | 70.8k |
| :6543 | Jetnet | UDP | Network Services | caution | 65.3k |
| :5938 | TeamViewer | TCPUDP | Remote Access | caution | 65.0k |
| :8291 | Winbox MikroTik Admin | TCP | Security | caution | 62.9k |
| :3233 | WhiskerControl Protocol | TCPUDP | Network Services | caution | 61.9k |
| :3268 | Microsoft Global Catalog (GC) | TCPUDP | Security | caution | 54.6k |
| :135 | Microsoft EPMAP | TCPUDP | Security | caution | 51.9k |
| :3128 | Tatsoft Default HTTP Proxy | TCP | Web Services | caution | 46.8k |
risk mix of the 8 listed
- caution100%
0 of 8 encrypted