Port 162: SNMP trap
Receives SNMP notifications from devices.
- Port
- 162
- Protocol
- UDP
- Service
- SNMP trap
- Exposure
- Do not expose to the internet
What is port 162 used for?
Alerts sent by network gear to a monitoring server.
Is it safe to expose port 162 to the internet?
Internal only.
If port 162 seems closed or unreachable
- Check that the SNMP trap service is running and listening on port 162, not only on 127.0.0.1.
- Check the firewall on the host itself (Windows Defender Firewall, iptables, nftables, ufw) for a rule that allows UDP 162.
- If the host is behind a router, confirm the forwarding rule points to the correct internal address and that your internet provider does not use carrier-grade NAT.
- Test from outside your own network. A port can be open locally and blocked at the edge, or the other way round.
Using port 162 safely
Treat port 162 as an internal-only service. Reach it through a VPN or an SSH tunnel, restrict it by source address, and keep the software that listens on it patched.
Check whether port 162 is open on your host
The check connects from our server, so it shows what the internet can reach.
Open the port checker