Port 4372LAN2CAN Data

TCP/UDP 4372 is assigned to LAN2CAN Data, registered to Phil Tolson; no common deployment is documented.

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
1/10

safe

lookups
0

rank 993 of 5,154 · top 19%

also known as l2c-data

Technical Details

what runs on :4372

LAN2CAN Data is registered on port :4372 over tcp and udp to Phil Tolson, assigned July 2008. We don't have a technical write-up for it beyond the IANA registry entry.

In nmap's internet-wide scan data this port is never observed open, so if it's open on your network it's more likely a custom or misconfigured service than the registered one.

find what's listening on :4372

this machine
# linux
sudo ss -tulpn 'sport = :4372'

# macos / bsd
sudo lsof -nP -i :4372

# windows (then: tasklist /FI "PID eq <pid>")
netstat -ano | findstr :4372
another host
nmap -sV -p T:4372 <host>
sudo nmap -sU -sV -p U:4372 <host>

run it? the handshake, the implementations you meet in the wild and the flags that matter come from the engineers who do.

add technical details

Security Information

exposure of :4372

risk score

1/ 10safe

routine exposure. this port is rarely the way in on its own — keep it patched and logged and move on.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

no security notes recorded for :4372 yet

known exploits, hardening advice, what a compromise looks like — suggest an edit if you know its exposure.

ports registered around :4372, by lookups.

risk mix of the 8 listed

  • safe50%
  • caution50%

0 of 8 encrypted