2 entries are registered on port 1920. 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 |
|---|---|---|---|---|---|
| :1920 | IBM Tivoli Monitoring | TCPtls | Web Services | caution | 21.5k |
| :1920 | IBM Tivoli Directory Service (FERRET) | TCPUDP | Network Services | safe | 0 |
IBM Tivoli Monitoring Console over HTTPS provides a secure, web-based interface for monitoring and managing IT resources across an enterprise. It enables IT administrators to observe system health, performance, and application status, facilitating proactive management of hardware and software assets.
port 1920 as IBM Tivoli Monitoring →IBM Tivoli Directory Service FERRET is assigned to TCP and UDP port 1920.
port 1920 as IBM Tivoli Directory Service (FERRET) →The registry says what 1920 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 ':1920\b'lsof -nP -iTCP:1920 -sTCP:LISTENnetstat -ano | findstr :1920On 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 1920 — 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