2 entries are registered on port 9060. 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 |
|---|---|---|---|---|---|
| :9060 | WebSphere Admin Console | TCP | Web Services | caution | 23.0k |
| :9060 | CardWeb realtime device data | UDP | — | safe | 0 |
The WebSphere Application Server Administration Console is a web-based interface that allows administrators to configure, deploy, monitor, and manage applications and resources on IBM WebSphere servers. It plays a critical role in enterprise environments running Java EE applications.
port 9060 as WebSphere Admin Console →UDP port 9060 is assigned to CardWeb realtime device data, a CardWare service with no established public deployment.
port 9060 as CardWeb realtime device data →The registry says what 9060 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 ':9060\b'lsof -nP -iTCP:9060 -sTCP:LISTENnetstat -ano | findstr :9060On 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 9060 — 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