Port 162 SNMPTRAP
Port 162 is the IANA-assigned snmptrap port for SNMPTRAP (TCP / UDP).
What is port 162 used for?
Port 162 is assigned to snmptrap and uses TCP / UDP. The IANA registry describes the service as “SNMPTRAP”. It sits in the well-known range, which operating systems reserve for core network services, so software expects it at this number by default.
Ports are the transport-layer address a service listens on. A client that wants to reach snmptrap connects to port 162. A TCP connection is refused when nothing is listening, while a UDP request simply goes unanswered. That is why a port conflict appears whenever two processes try to bind the same number.
Use the commands below to confirm whether port 162 is actually in use before you change firewall rules. Blocking the port stops new inbound traffic at the firewall, but it does not stop a local process from listening, and it does not remove the service from the machine.
Browse all Monitoring and metrics ports
Source: IANA Service Name and Transport Protocol Port Number Registry. Registered assignee: [Marshall_Rose].
Check and block port 162
Copy-ready commands for the protocols assigned to this port. Run the check first, then block only what should not be reachable.
Check on Linux
sudo ss -tlpn 'sport = :162'
sudo ss -ulpn 'sport = :162'Check on Windows
Get-NetTCPConnection -LocalPort 162 -State Listen -ErrorAction SilentlyContinue
Get-NetUDPEndpoint -LocalPort 162 -ErrorAction SilentlyContinueBlock with UFW
sudo ufw deny 162/tcp
sudo ufw deny 162/udpBlock with iptables
sudo iptables -A INPUT -p tcp --dport 162 -j DROP
sudo iptables -A INPUT -p udp --dport 162 -j DROPThese commands are examples for a typical host. Check the listener before you change firewall rules, and persist iptables rules with iptables-save or netfilter-persistent. On Windows, use Windows Defender Firewall or New-NetFirewallRule for persistent blocks. The iptables rules here cover IPv4; mirror them with ip6tables if IPv6 is enabled.
Is port 162 safe to expose?
SNMP traps can leak operational data to unauthorised collectors; restrict receivers to your monitoring network. Expose this port only when the service is actually needed. Keep it patched, prefer an encrypted alternative, and limit source addresses with a firewall allowlist.
Where port 162 is usually used
Most traffic on port 162 falls into these scenarios. The demo below is a safe way to confirm the listener before you change anything.
- Scrapers such as Prometheus pulling metrics from port 162 on a schedule.
- Dashboards and alerting rules querying the same endpoint.
- Incident reviews comparing metrics before and after a deployment.
Watch for SNMP traps
Trap receivers listen on UDP 162; there is no request to send, so watch incoming traps.
sudo tcpdump -ni any udp port 162Common problems with port 162
Connection refused or timed out
Refused usually means the host is reachable but nothing is listening on port 162. A timeout more often means a firewall drop, a wrong host or a service bound to a different interface.
Port already in use
Find the process holding the port with sudo ss -tlpn 'sport = :162' or sudo lsof -i :162. Stop that process or configure it to bind another port; killing it without identifying it can take down a production service.
Firewall rule did not survive a reboot
UFW and Windows Firewall keep rules across restarts. Raw iptables rules do not: save them with iptables-save or the netfilter-persistent package, and re-apply after upgrades that reset the ruleset.
The port is blocked but still reachable
A firewall rule filters inbound traffic; it does not close the listener. Confirm with the check command above and bind the service to 127.0.0.1 when only local clients need it.
Port 162 at a glance
| Port number | 162 |
|---|---|
| Service name | snmptrap |
| Transport protocol | TCP / UDP |
| Category | Monitoring and metrics |
| Range | Well-known port (0–1023) |
| Risk level | Medium |
| Registered assignee | [Marshall_Rose] |
| Registry description | SNMPTRAP |
| Source | IANA Service Name and Transport Protocol Port Number Registry |
Frequently asked questions
What is port 162 used for?
Port 162 (SNMPTRAP) uses TCP / UDP. SNMPTRAP.
How do I check if port 162 is open?
On Linux run `sudo ss -tlpn 'sport = :162'` and `sudo ss -ulpn 'sport = :162'`. On Windows run `Get-NetTCPConnection -LocalPort 162 -State Listen -ErrorAction SilentlyContinue` and `Get-NetUDPEndpoint -LocalPort 162 -ErrorAction SilentlyContinue` in PowerShell. If the port is open, the output shows a process listening on port 162; empty output usually means nothing is bound to it.
How do I block port 162?
With UFW run `sudo ufw deny 162/tcp` and `sudo ufw deny 162/udp`. With iptables run `sudo iptables -A INPUT -p tcp --dport 162 -j DROP` and `sudo iptables -A INPUT -p udp --dport 162 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot.
Is port 162 safe to expose?
SNMP traps can leak operational data to unauthorised collectors; restrict receivers to your monitoring network. Nevertheless, expose this port only when the service is actually needed. Keep it patched, prefer an encrypted alternative, and limit source addresses with a firewall allowlist.
Related ports
Primary data: IANA Service Name and Transport Protocol Port Number Registry.
Last reviewed 2026-10-30 · Methodology · About · Privacy