01Internet ADT Discovery Protocoludp · iana-registered · risk 1/10
UDP port assigned to the Internet ADT Discovery Protocol; no common public deployment is documented.
port 4169 as Internet ADT Discovery Protocol →Port 41692 services
2 entries are registered on port 4169. 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 | |||
|---|---|---|---|---|---|
| :4169 | Internet ADT Discovery Protocol | UDP | Network Services | safe | 0 |
| :4169 | Automation Drive Interface Transport | TCP | — | safe | 0 |
02Automation Drive Interface Transporttcp · iana-registered · risk 1/10
TCP port 4169 is assigned to the Automation Drive Interface Transport (IADT).
port 4169 as Automation Drive Interface Transport →filed underNetwork Services
Which one is on your host
The registry says what 4169 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 ':4169\b'- macos
lsof -nP -iTCP:4169 -sTCP:LISTEN- windows
netstat -ano | findstr :4169
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 4169 — 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