01Veritas TCP1tcp · iana-registered · risk 1/10
Veritas TCP1 is the IANA label for TCP/2802; no common deployment or protocol behavior is documented.
port 2802 as Veritas TCP1 →Port 28022 services
2 entries are registered on port 2802. 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 | |||
|---|---|---|---|---|---|
| :2802 | Veritas TCP1 | TCP | — | safe | 0 |
| :2802 | Veritas UDP1 | UDP | — | safe | 0 |
02Veritas UDP1udp · iana-registered · risk 1/10
UDP/2802 is assigned to Veritas UDP1, registered to Russ Thrasher; no common public deployment is documented.
port 2802 as Veritas UDP1 →Which one is on your host
The registry says what 2802 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 ':2802\b'- macos
lsof -nP -iTCP:2802 -sTCP:LISTEN- windows
netstat -ano | findstr :2802
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 2802 — 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