01Desktop Data UDP 3 (NESS application)udp · iana-registered · risk 1/10
An obscure UDP assignment for Desktop Data UDP 3, described by IANA as a NESS application.
port 8891 as Desktop Data UDP 3 (NESS application) →Port 88912 services
2 entries are registered on port 8891. 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
- udp · tcp
- 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 | |||
|---|---|---|---|---|---|
| :8891 | Desktop Data UDP 3 (NESS application) | UDP | — | safe | 0 |
| :8891 | Desktop Data TCP 3 (NESS application) | TCP | — | safe | 0 |
02Desktop Data TCP 3 (NESS application)tcp · iana-registered · risk 1/10
TCP 8891 is assigned to Desktop Data TCP 3 for the NESS application; its public use is not established.
port 8891 as Desktop Data TCP 3 (NESS application) →Which one is on your host
The registry says what 8891 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 ':8891\b'- macos
lsof -nP -iTCP:8891 -sTCP:LISTEN- windows
netstat -ano | findstr :8891
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 8891 — 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