01NewsEDGE client broadcastudp · iana-registered · risk 1/10
UDP 8890 is assigned to NewsEDGE client broadcast, an obscure service registered to Fred Yao.
port 8890 as NewsEDGE client broadcast →Port 88902 services
2 entries are registered on port 8890. 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 | |||
|---|---|---|---|---|---|
| :8890 | NewsEDGE client broadcast | UDP | Network Services | safe | 0 |
| :8890 | Desktop Data TCP 2 | TCP | — | safe | 0 |
02Desktop Data TCP 2tcp · iana-registered · risk 1/10
TCP/8890 is assigned to Desktop Data TCP 2, but no common listener or protocol behavior is established.
port 8890 as Desktop Data TCP 2 →filed underNetwork Services
Which one is on your host
The registry says what 8890 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 ':8890\b'- macos
lsof -nP -iTCP:8890 -sTCP:LISTEN- windows
netstat -ano | findstr :8890
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 8890 — 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