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