2 entries are registered on port 9080. 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 |
|---|---|---|---|---|---|
| :9080 | Groove RPC | TCPUDP | Web Services | caution | 70.8k |
| :9080 | WebSphere HTTP Transport (default) | TCP | Web Services | caution | 51.6k |
GLRPC stands for Groove Lightweight Remote Procedure Call, a proprietary protocol used by the Groove Collaboration software suite, which was later integrated into Microsoft SharePoint Workspace before its discontinuation. It facilitated real-time communication, synchronization, and data sharing within Groove's peer-to-peer workspace environment.
port 9080 as Groove RPC →Port 9080 is commonly used by IBM WebSphere Application Server's HTTP Transport as the default HTTP listener port. It facilitates web-based communication between clients and the application server, typically used to serve dynamic content, REST/SOAP APIs, or facilitate internal administrative functions during development and testing phases.
port 9080 as WebSphere HTTP Transport (default) →The registry says what 9080 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 ':9080\b'lsof -nP -iTCP:9080 -sTCP:LISTENnetstat -ano | findstr :9080On 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 9080 — 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