01M3DA Discoveryudp · iana-registered · risk 1/10
UDP discovery for M3DA, an efficient machine-to-machine communications protocol.
port 44900 as M3DA Discovery →Port 449002 services
2 entries are registered on port 44900. 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 | |||
|---|---|---|---|---|---|
| :44900 | M3DA Discovery | UDP | IoT | safe | 0 |
| :44900 | M3DA | TCP | Network Services | safe | 0 |
02M3DAtcp · iana-registered · risk 2/10
M3DA is a binary machine-to-machine protocol used by devices and servers in the Eclipse Mihini ecosystem.
port 44900 as M3DA →Which one is on your host
The registry says what 44900 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 ':44900\b'- macos
lsof -nP -iTCP:44900 -sTCP:LISTEN- windows
netstat -ano | findstr :44900
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 44900 — 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