2 entries are registered on port 16000. 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 |
|---|---|---|---|---|---|
| :16000 | shroudBNC | TCP | Network Services | caution | 4.0k |
| :16000 | Administration Server Access | TCP | Remote Access | safe | 0 |
shroudBNC is a popular IRC bouncer allowing users to maintain persistent connections to IRC networks even while disconnected, offering session management, privacy, and convenience for IRC users across various clients.
port 16000 as shroudBNC →TCP service for Administration Server Access, assigned under the fmsas service name.
port 16000 as Administration Server Access →The registry says what 16000 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 ':16000\b'lsof -nP -iTCP:16000 -sTCP:LISTENnetstat -ano | findstr :16000On 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 16000 — 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