01netcomm2udp · iana-registered · risk 1/10
Unidentified UDP service assigned as netcomm2 to Bulent Kasman.
port 1676 as netcomm2 →Port 16762 services
2 entries are registered on port 1676. 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
02netcomm1tcp · iana-registered · risk 1/10
TCP port 1676 is listed for netcomm1, with no registrant or protocol details recorded.
port 1676 as netcomm1 →Which one is on your host
The registry says what 1676 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 ':1676\b'- macos
lsof -nP -iTCP:1676 -sTCP:LISTEN- windows
netstat -ano | findstr :1676
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 1676 — 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