2 entries are registered on port 9091. 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 |
|---|---|---|---|---|---|
| :9091 | Openfire Admin Console (SSL) | TCPtls | Web Services | caution | 28.3k |
| :9091 | xmltec-xmlmail | TCPUDP | safe | 0 |
Openfire's secured web-based Administration Console operates on port 9091, providing administrators encrypted access to configure and manage the Openfire real-time collaboration server. It offers a user-friendly interface for server setup, user management, group chat configuration, and plugin management, all protected by SSL encryption to ensure secure administrator connections.
port 9091 as Openfire Admin Console (SSL) →XML-based mail service identified as xmltec-xmlmail, with little publicly documented deployment.
port 9091 as xmltec-xmlmail →The registry says what 9091 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 ':9091\b'lsof -nP -iTCP:9091 -sTCP:LISTENnetstat -ano | findstr :9091On 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 9091 — 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