Is port 2375 (Docker API) safe to expose?
Docker daemon (unencrypted TCP). Exposing it to the internet is a critical risk.
Why exposing port 2375 is risky
An exposed Docker daemon on 2375 is root on the host for anyone who reaches it — a full compromise.
How to check if it's exposed
From outside your network, a quick nmap -p 2375 <your-ip> (or an external port scanner) shows whether 2375 answers. On the host, ss -tlnp | grep :2375 shows what's listening and on which interface — it should be a private address, not 0.0.0.0.
How to secure it
- Never expose the daemon on TCP; use the local socket.
- If TCP is unavoidable, require TLS client certificates (2376).
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.