2 entries are registered on port 5223. 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 |
|---|---|---|---|---|---|
| :5223 | XMPP over SSL | TCPtls | Security | caution | 16.3k |
| :5223 | HP Virtual Machine Group Management | TCPUDP | Virtualization | safe | 0 |
Port 5223 is primarily used for secure client connections in the Extensible Messaging and Presence Protocol (XMPP). It enables encrypted communication between XMPP clients and servers, facilitating secure instant messaging, presence information exchange, and collaboration applications. Historically, this port has been used to support SSL/TLS encrypted connections for clients needing to protect data in transit.
port 5223 as XMPP over SSL →HP Virtual Machine Group Management traffic assigned to TCP and UDP port 5223.
port 5223 as HP Virtual Machine Group Management →The registry says what 5223 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 ':5223\b'lsof -nP -iTCP:5223 -sTCP:LISTENnetstat -ano | findstr :5223On 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 5223 — 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