Registry assignments, software defaults and local listeners are different things. A port number alone does not identify or secure a service.
Software Using This Port (2 software)
Community software entries: links are references, not individual verification.
Usage Suggestions
- Before using port 389, please confirm it is not occupied by other services
- If you encounter port conflicts, consider using other ports or stopping the occupying service
Frequently asked questions
What is port 389 used for?
Port 389 sits in the Directory Services category. This page lists the registered purpose and the software commonly associated with it; to see what is actually listening on a specific machine, check the process with ss/netstat.
Is port 389 TCP or UDP?
The registered protocol on this page is TCP. The same number behaves independently on each protocol: TCP may be listening while UDP is idle, so check them separately.
How do I check if port 389 is in use?
On Linux: sudo ss -tlnp 'sport = :389' for an exact port match. On macOS: sudo lsof -nP -iTCP:389 -sTCP:LISTEN. On Windows PowerShell: Get-NetTCPConnection -LocalPort 389 -State Listen. A listener counts as confirmed only when you can see the bind address and process name; without root/admin you will not see other users' processes.
Is port 389 secure? Should I open it in my firewall?
A port number has no inherent security — it depends on whether the listening service is correctly configured and whether it needs exposure at all. Keep loopback/internal-only services firewalled; where public access is required, pair it with source restrictions, VPN or authentication.
Quick Info
- Port
- 389
- Protocol
- TCP
- Categories
- Directory Services
- Usage Status
- 2 software in use
Related Ports
Need Help?
If you find incorrect information or need to add more, please submit correction information.
Submit Correction