01LAN2CAN Discoveryudp · iana-registered · risk 1/10
UDP port 4371 is assigned to LAN2CAN Discovery; no established public use beyond the assignment is known.
port 4371 as LAN2CAN Discovery →Port 43712 services
2 entries are registered on port 4371. 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 | |||
|---|---|---|---|---|---|
| :4371 | LAN2CAN Discovery | UDP | Network Services | safe | 0 |
| :4371 | LAN2CAN Control | TCP | — | safe | 0 |
02LAN2CAN Controltcp · iana-registered · risk 1/10
TCP port 4371 is assigned to LAN2CAN Control, registered by Phil Tolson.
port 4371 as LAN2CAN Control →filed underNetwork Services
Which one is on your host
The registry says what 4371 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 ':4371\b'- macos
lsof -nP -iTCP:4371 -sTCP:LISTEN- windows
netstat -ano | findstr :4371
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 4371 — 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