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