01Cisco RSRB Priority 3tcp · udp · iana-registered · risk 1/10
Cisco Remote Source-Route Bridging traffic using its priority-3 service.
port 1989 as Cisco RSRB Priority 3 →Port 19892 services
2 entries are registered on port 1989. 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.
- entries
- 2
- transport
- tcp · udp
- in transit
- 0/2
- worst risk
- 1/10
services registered on this number
2 transports in use
entries encrypted on the wire
2 of 2 iana-registered
Services on this port
| port | service | risk | |||
|---|---|---|---|---|---|
| :1989 | Cisco RSRB Priority 3 | TCPUDP | Network Services | safe | 0 |
| :1989 | MHSnet | TCPUDP | Network Services | safe | 0 |
02MHSnettcp · udp · iana-registered · risk 1/10
MHSnet system traffic uses TCP and UDP port 1989 for an obscure messaging service.
port 1989 as MHSnet →filed underNetwork Services
Which one is on your host
The registry says what 1989 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.
- linux
ss -ltnp | grep ':1989\b'- macos
lsof -nP -iTCP:1989 -sTCP:LISTEN- windows
netstat -ano | findstr :1989
On 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 1989 — 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