Port 162: SNMP trap
UDP 162 is the port for SNMP traps and notifications. Only between your devices and your monitoring server.
| Service | SNMP traps and notifications |
|---|---|
| Protocol | UDP |
| Exposure risk | Medium: expose with care |
| Range | Well-known (0–1023): binding needs root/admin on Unix |
Port 162 is UDP-only. UDP has no handshake, so no online checker can reliably tell open from filtered; test with the service's own client.
What port 162 does
Network devices push alerts (link down, high temperature, reboot) to a monitoring server listening on UDP 162.
Should port 162 be open?
Only between your devices and your monitoring server.
Find what's listening on port 162
- Linux:
sudo ss -tulpn | grep :162 - macOS:
sudo lsof -nP -i :162 - Windows:
netstat -ano | findstr :162, then look up the PID in Task Manager.
Open or block it in a firewall
- ufw:
sudo ufw allow 162/udp(ordeny) - firewalld:
sudo firewall-cmd --add-port=162/udp --permanent && sudo firewall-cmd --reload - Windows:
New-NetFirewallRule -DisplayName "Port 162" -Direction Inbound -Protocol UDP -LocalPort 162 -Action Allow
Port assignment per the IANA Service Name and Transport Protocol Port Number Registry. Test several ports at once with the port scanner, or any port with the open port checker.
Questions about port 162
What is port 162 used for?
SNMP traps and notifications. Network devices push alerts (link down, high temperature, reboot) to a monitoring server listening on UDP 162.
Is port 162 TCP or UDP?
UDP. SNMP trap uses UDP port 162.
Is it safe to open port 162?
Medium: expose with care. Only between your devices and your monitoring server.
How do I check if port 162 is open?
Port 162 is UDP-only, which has no handshake, so an online TCP checker can't confirm it. Use the service's own client to test, and check what is listening locally with
ss -ulpn | grep :162 (Linux) or netstat -ano | findstr :162 (Windows).