2 entries are registered on port 5106. 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
1 transport in use
entries encrypted on the wire
1 of 2 iana-registered
| port | service | proto | category | risk | views |
|---|---|---|---|---|---|
| :5106 | A-Talk | TCP | Voice and Chat | caution | 11.1k |
| :5106 | Actifio UDS Agent | TCP | — | safe | 0 |
Port 5106 is commonly associated with A-Talk, a communication or messaging protocol/application. It is primarily used to facilitate messaging, signaling, or control data exchange between clients and servers within the A-Talk ecosystem. Typically leveraging TCP connectivity, this port ensures reliable data transmission required for messaging synchronization and real-time exchanges within the application environment.
port 5106 as A-Talk →TCP port 5106 is assigned to the Actifio UDS Agent.
port 5106 as Actifio UDS Agent →The registry says what 5106 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 ':5106\b'lsof -nP -iTCP:5106 -sTCP:LISTENnetstat -ano | findstr :5106On 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 5106 — 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