Port 161 — SNMP
UDP well-known
What runs on port 161
Network device monitoring and management.
Security considerations
SNMP v1 and v2c authenticate with a community string sent in clear text, and "public" is still a common default. Use v3, or firewall it to the monitoring host.
Checking whether something is listening
# Linux / macOS — what is bound to the port
sudo lsof -i :161
sudo ss -lntp | grep :161
# Windows
netstat -ano | findstr :161
Get-NetTCPConnection -LocalPort 161
# is it reachable from outside?
nc -zv example.com 161
curl -v telnet://example.com:161
Freeing the port
# find the process, then stop it
sudo lsof -ti :161 | xargs kill # Linux / macOS
netstat -ano | findstr :161 # note the PID, then:
taskkill /PID <pid> /F # Windows
Should this port be open to the internet?
Usually not. Expose it only if a specific external client needs it, and restrict by source address where you can.
Quick reference
| Port | 161 |
| Protocol | UDP |
| Service | SNMP |
| Range | Well-known (0–1023) — binding requires root on Unix |
Frequently asked questions
What is port 161 used for?
Network device monitoring and management.
Is it safe to open port 161?
SNMP v1 and v2c authenticate with a community string sent in clear text, and "public" is still a common default. Use v3, or firewall it to the monitoring host.
How do I check if port 161 is open?
Locally, sudo lsof -i :161 on macOS or Linux, or netstat -ano | findstr :161 on Windows. From outside, nc -zv host 161 tells you whether anything answers.
Why do I get "address already in use" on port 161?
Another process is bound to it — often a previous run of your own program that did not exit cleanly. Find it with lsof -ti :161 and stop it, or configure your application to use a different port.
Can I change the port this service uses?
Almost always yes, in the service's configuration. Moving off a default port reduces automated scan noise, but it is obfuscation rather than security — a real attacker scans all 65,535.