2 entries are registered on port 5104. 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.
services registered on this number
2 transports in use
entries encrypted on the wire
1 of 2 iana-registered
| port | service | proto | category | risk | views |
|---|---|---|---|---|---|
| :5104 | IBM Netcool Impact HTTP | TCP | Network Services | caution | 22.2k |
| :5104 | TinyMessage | UDP | — | safe | 0 |
Port 5104 is primarily used by IBM Tivoli Netcool/Impact, a key policy-driven analytics and event management component within the IBM Tivoli system management suite. It typically hosts an HTTP service for receiving API calls, handling event processing, and integrating operational data to support real-time decision-making and automation.
port 5104 as IBM Netcool Impact HTTP →UDP port 5104 is assigned to TinyMessage, a little-documented service registered to Josip Medved.
port 5104 as TinyMessage →The registry says what 5104 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.
ss -ltnp | grep ':5104\b'lsof -nP -iTCP:5104 -sTCP:LISTENnetstat -ano | findstr :5104On 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 5104 — 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