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