- 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 1650: nkdn
Port 1650 is assigned by IANA to nkd (nkdn).
How nkd works
Other servicesThe client sends a request to port 1650 and the nkd 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 1650 dangerous?
We have no specific security note for port 1650. Its risk depends on the program actually listening on it. General advice for other services services:
IANA registry entries for port 1650
| Service | Port | Transport | Description | Reference | Updated |
|---|---|---|---|---|---|
| nkd | 1650 | TCP, UDP | nkdn | - | - |
// source: IANA service name and port number registry
Which program uses port 1650, and is it reachable?
Linux
sudo ss -ltnup 'sport = :1650' # process listening on 1650
sudo lsof -nP -i :1650macOS
sudo lsof -nP -i :1650
Windows (PowerShell)
Get-NetTCPConnection -LocalPort 1650 -State Listen | Select LocalAddress, OwningProcess Get-NetUDPEndpoint -LocalPort 1650 netstat -ano | findstr :1650
From another machine
nmap -p 1650 -sV <host> sudo nmap -sU -p 1650 <host> nc -zv <host> 1650
Block it in the firewall
sudo ufw deny 1650/tcp # Linux (ufw) New-NetFirewallRule -DisplayName "Block 1650" -Direction Inbound -LocalPort 1650 -Protocol TCP -Action Block # Windows
What is port 1650 used for?
Port 1650 is assigned by IANA to nkd (nkdn).
Is port 1650 TCP or UDP?
Port 1650 is registered for TCP and UDP.
Is it safe to open port 1650?
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 1650 is open?
On Linux run "ss -ltnup 'sport = :1650'", on macOS "lsof -nP -i :1650", and on Windows "netstat -ano | findstr :1650" to see the local process. From another machine, "nmap -p 1650 <host>" shows whether it is reachable.