Is port 389 (LDAP) safe to expose?
LDAP — directory services. Exposing it to the internet is high risk.
Why exposing port 389 is risky
Exposed LDAP can leak the directory and, unencrypted, credentials. It also factors into relay attacks.
How to check if it's exposed
From outside your network, a quick nmap -p 389 <your-ip> (or an external port scanner) shows whether 389 answers. On the host, ss -tlnp | grep :389 shows what's listening and on which interface — it should be a private address, not 0.0.0.0.
How to secure it
- Use LDAPS (636) and restrict access to internal hosts.
- Never expose directory services to the internet.
SkyShield watches what's really exposed
SkyShield follows your firewall rules through to the container and shows what the internet can actually reach. Free for one server, then from $49 per server a month. Start free.