Port 5162SNMP Notification over SSH

TCP port 5162 is the IETF-defined SSH transport for receiving SNMP notifications, an uncommon alternative to UDP traps.

transport: tcp
in transit: encrypted
assignment: official
risk: 3/10
lookups: 0

also known as snmpssh-trap, SNMP over SSH, RFC 5592

Technical Details

what runs on :5162

This is a TCP endpoint for SNMP notifications carried through an SSH transport session, rather than ordinary SNMP trap datagrams over UDP. The SSH session provides the protected channel over which SNMP messages are exchanged; the model uses SSH authentication and encrypted, integrity-protected transport. Port 5162 is the notification port, distinct from port 5161, commonly associated with SNMP over SSH for request/response traffic. The model is specified in RFC 5592 and is rarely encountered compared with SNMP over UDP.

Security Information

exposure of :5162

risk score

3/ 10caution

worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.

security averages 3.1 across 385 ports — this one sits 0.1 below.

in transit

encrypted

payloads are protected on the wire

assignment

official

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

reachable over

tcp

every listening transport is another surface to filter at the edge

security overview

SSH protects the traffic in normal use, but the listener still accepts network connections and should generally be limited to expected notification senders or a management network. An attacker can probe the SSH endpoint and attempt authentication or exploit weaknesses in its implementation; use strong SSH authentication and keep the software patched. This is not the conventional UDP port 162 trap service.

Record

iana registry entry

port: :5162
service: SNMP Notification over SSH
transport: TCP
encryption: tls / encrypted
assignment: iana registered
risk: 3/10caution
category: Security Network Services
usage: This port is for SNMP notification receivers using the Secure Shell Transport Model defined in RFC 5592. It is an uncommon alternative to the usual UDP-based SNMP trap listener on port 162; finding it open does not imply that a general-purpose SSH shell is available.
lookups: 0rank 993
added: 2026-10-07
updated: 2026-10-07
references: IANA service name registry — port 5162
RFC 5592

Something wrong?

This record is maintained by the engineers who use port 5162. Every field on it is editable — change what's wrong, say how you know, and a reviewer publishes it, usually within a minute. Last touched 2026-10-07.

01edit any field on a page of its own
02a model checks it for accuracy and spam
03clean and confident goes live immediately

edit this record →back to the registry

Related Ports

all 385 in security →

the 8 most looked-up other ports in security — 385 ports carry that label.

port	service	proto	category	risk	views
:8881	Atlasz Secure Server	TCP	Web Services	caution	67.6k
:443	HTTPS	TCPtls	Web Services	caution	65.9k
:8291	Winbox MikroTik Admin	TCP	Security	caution	62.9k
:3268	Microsoft Global Catalog (GC)	TCPUDP	Security	caution	54.6k
:135	Microsoft EPMAP	TCPUDP	Security	caution	51.9k
:3128	Squid Proxy HTTP	TCP	Web Services	caution	45.8k
:8080	HTTP Alternate	TCP	Web Services	caution	44.9k
:7000	Vuze HTTPS Tracker	TCPtls	Security	caution	28.9k

risk mix of the 8 listed

caution100%

2 of 8 encrypted

Port :5162SNMP Notification over SSH

Technical Details

Security Information

Related Ports

Port 5162SNMP Notification over SSH