01DoIP Vehicle Discoveryudp · iana-registered · risk 5/10
UDP port 13400 carries DoIP vehicle-discovery requests and announcements on automotive networks.
port 13400 as DoIP Vehicle Discovery →Port 134002 services
2 entries are registered on port 13400. 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
- 8/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 | |||
|---|---|---|---|---|---|
| :13400 | DoIP Vehicle Discovery | UDP | Network Services | caution | 0 |
| :13400 | Diagnostics over Internet Protocol (DoIP) | TCP | Network Services | risk | 0 |
02Diagnostics over Internet Protocol (DoIP)tcp · iana-registered · risk 8/10
DoIP carries automotive diagnostic traffic between diagnostic testers and vehicle ECUs over Ethernet.
port 13400 as Diagnostics over Internet Protocol (DoIP) →Which one is on your host
The registry says what 13400 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 ':13400\b'- macos
lsof -nP -iTCP:13400 -sTCP:LISTEN- windows
netstat -ano | findstr :13400
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 13400 — 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