2 entries are registered on port 16384. 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 |
|---|---|---|---|---|---|
| :16384 | Iron Mountain Backup | UDP | File Transfer | caution | 7.4k |
| :16384 | connected | TCPUDP | — | safe | 0 |
Port 16384 is primarily used by Iron Mountain Digital's online backup services, which provide secure and automated remote data backup solutions for enterprises. This port facilitates the transfer of backup data between client systems and Iron Mountain's data centers, relying on UDP for efficient communication during large data transfers.
port 16384 as Iron Mountain Backup →An obscure TCP/UDP assignment for Connected Corp, with no widely recognized protocol or common listener associated with it.
port 16384 as connected →The registry says what 16384 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 ':16384\b'lsof -nP -iTCP:16384 -sTCP:LISTENnetstat -ano | findstr :16384On 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 16384 — 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