01SNMP Trap over DTLSudp · iana-registered · risk 3/10
Encrypted SNMP trap and notification traffic carried over DTLS on UDP port 10162.
port 10162 as SNMP Trap over DTLS →Port 101622 services
2 entries are registered on port 10162. 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
- 2/2
- worst risk
- 3/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 | |||
|---|---|---|---|---|---|
| :10162 | SNMP Trap over DTLS | UDPtls | Security | caution | 0 |
| :10162 | SNMP Trap over TLS | TCPtls | Security | safe | 0 |
02SNMP Trap over TLStcp · iana-registered · risk 2/10
TCP port 10162 is the standardized TLS-protected listener for receiving SNMP trap notifications.
port 10162 as SNMP Trap over TLS →Which one is on your host
The registry says what 10162 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 ':10162\b'- macos
lsof -nP -iTCP:10162 -sTCP:LISTEN- windows
netstat -ano | findstr :10162
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 10162 — 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