2 entries are registered on port 2053. 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 |
|---|---|---|---|---|---|
| :2053 | knetd Demultiplexer | TCP | Security | safe | 17.2k |
| :2053 | Lot105 DSuper Updates | UDP | Network Services | caution | 12.4k |
knetd is a network service used primarily as a Kerberos protocol multiplexer or demultiplexer, which assists with forwarding different Kerberos-related traffic streams to the correct local service. It facilitates enhanced management of authentication services across distributed systems leveraging Kerberos security.
port 2053 as knetd Demultiplexer →Port 2053 is utilized primarily for Lot105 DSuper Updates over UDP. It serves specific update and communication functions tied to proprietary or specialized devices or services, facilitating the delivery and synchronization of software patches and system data without relying on TCP.
port 2053 as Lot105 DSuper Updates →The registry says what 2053 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 ':2053\b'lsof -nP -iTCP:2053 -sTCP:LISTENnetstat -ano | findstr :2053On 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 2053 — 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