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