01AllJoyn Multiplexed Constrained Messaging (MCM)udp · iana-registered · risk 1/10
UDP contact port assigned for AllJoyn Multiplexed Constrained Messaging (MCM).
port 9955 as AllJoyn Multiplexed Constrained Messaging (MCM) →Port 99552 services
2 entries are registered on port 9955. It is a registered port (1024–49151) — IANA records an assignee, but nothing stops other software from listening here, which is why the number carries more than one entry.
- entries
- 2
- transport
- udp · tcp
- in transit
- 0/2
- worst risk
- 2/10
services registered on this number
2 transports in use
entries encrypted on the wire
2 of 2 iana-registered
Services on this port
| port | service | risk | |||
|---|---|---|---|---|---|
| :9955 | AllJoyn Multiplexed Constrained Messaging (MCM) | UDP | IoT | safe | 0 |
| :9955 | AllJoyn Standard Messaging | TCP | Network Services | safe | 0 |
02AllJoyn Standard Messagingtcp · iana-registered · risk 2/10
TCP port 9955 is the IANA contact port for AllJoyn standard messaging, used by AllJoyn-enabled devices and applications.
port 9955 as AllJoyn Standard Messaging →Which one is on your host
The registry says what 9955 is registered to. What is listening on it right now is decided by the host, and only the host can be asked. Each of these prints the process behind the socket.
- linux
ss -ltnp | grep ':9955\b'- macos
lsof -nP -iTCP:9955 -sTCP:LISTEN- windows
netstat -ano | findstr :9955
On Linux and Windows the process name comes back with the socket; on macOS lsof needs sudo to name a process that isn't yours. Match what it prints against the 2 entries above.
A port number is not a service. Anything may listen on 9955 — what you actually met is decided by the host, not the registry. If a service is missing here, it belongs in the registry.
contribute an entry