- Close the port if nothing on the host needs it.
- Identify the process that listens on it (commands below) before opening it in a firewall.
- Expose a service only to the networks that use it.
Port 1652: xnmp
Port 1652 is assigned by IANA to xnmp (xnmp).
How xnmp works
Other servicesThe client sends a request to port 1652 and the xnmp service answers.
- Transport
- TCP · UDP
- Exposure risk
- not rated depends on the program listening
- Encryption
- Unknownnot stated by the registry
- IANA status
- Assigned1 registered service
- Range
- Registered (1024-49151)
- Category
- Other services
Is port 1652 dangerous?
We have no specific security note for port 1652. Its risk depends on the program actually listening on it. General advice for other services services:
IANA registry entries for port 1652
| Service | Port | Transport | Description | Reference | Updated |
|---|---|---|---|---|---|
| xnmp | 1652 | TCP, UDP | xnmp | - | - |
// source: IANA service name and port number registry
Which program uses port 1652, and is it reachable?
Linux
sudo ss -ltnup 'sport = :1652' # process listening on 1652
sudo lsof -nP -i :1652macOS
sudo lsof -nP -i :1652
Windows (PowerShell)
Get-NetTCPConnection -LocalPort 1652 -State Listen | Select LocalAddress, OwningProcess Get-NetUDPEndpoint -LocalPort 1652 netstat -ano | findstr :1652
From another machine
nmap -p 1652 -sV <host> sudo nmap -sU -p 1652 <host> nc -zv <host> 1652
Block it in the firewall
sudo ufw deny 1652/tcp # Linux (ufw) New-NetFirewallRule -DisplayName "Block 1652" -Direction Inbound -LocalPort 1652 -Protocol TCP -Action Block # Windows
What is port 1652 used for?
Port 1652 is assigned by IANA to xnmp (xnmp).
Is port 1652 TCP or UDP?
Port 1652 is registered for TCP and UDP.
Is it safe to open port 1652?
It depends on the program that listens on it. Open it only for a service you know and only to the networks that need it. Close the port if nothing on the host needs it.
How do I check if port 1652 is open?
On Linux run "ss -ltnup 'sport = :1652'", on macOS "lsof -nP -i :1652", and on Windows "netstat -ano | findstr :1652" to see the local process. From another machine, "nmap -p 1652 <host>" shows whether it is reachable.