Port 2375 is the Docker daemon’s remote API without TLS. It is only open if dockerd has been started with -H tcp://0.0.0.0:2375 or the equivalent setting. It should not be reachable from the public internet.
- Port
- 2375
- Protocol
- TCP
- Service
- Docker Engine API (unencrypted)
- Expose to internet?
- No
Is port 2375 safe to open?
The Docker API on 2375 has no authentication. Anyone who reaches it can start a privileged container that mounts the host’s root filesystem, which is root access to the server. Exposed Docker APIs are found within hours and used to install cryptocurrency miners.
How to secure Docker Engine API (unencrypted)
- Remove the
tcp://host from /etc/docker/daemon.json or the systemd unit and use the local socket only. - For remote management, use SSH:
DOCKER_HOST=ssh://user@host docker ps. - If you need TCP, use 2376 with mutual TLS (
--tlsverify). - Block 2375 at the firewall; note that Docker’s own iptables rules do not protect the daemon port.
Check if port 2375 is open
Linux: what is listening on this port
sudo ss -tlpn | grep ':2375 'Windows (PowerShell): what is listening
Get-NetTCPConnection -LocalPort 2375 -State Listen | Select-Object LocalAddress, OwningProcess, @{n='Process';e={(Get-Process -Id $_.OwningProcess).Name}}From another machine: is it reachable
nc -zv HOST 2375
# or
nmap -p 2375 HOST
# Windows
Test-NetConnection HOST -Port 2375Test the Docker Engine API (unencrypted) service itself
curl -s http://HOST:2375/versionRestrict port 2375 in the firewall
Replace 10.0.0.0/8 with the network or address that needs access. Docker publishes container ports through its own iptables rules, which bypass ufw; bind published ports to 127.0.0.1 (-p 127.0.0.1:2375:2375) instead of relying on the host firewall.
ufw: allow only your private network, deny everyone else
sudo ufw allow from 10.0.0.0/8 to any port 2375 proto tcp
sudo ufw deny 2375/tcpfirewalld: allow one source network only
sudo firewall-cmd --permanent --remove-port=2375/tcp
sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="10.0.0.0/8" port port="2375" protocol="tcp" accept'
sudo firewall-cmd --reloadiptables
sudo iptables -A INPUT -p tcp --dport 2375 -s 10.0.0.0/8 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 2375 -j DROPWindows Firewall (PowerShell, as Administrator)
New-NetFirewallRule -DisplayName "Block 2375 from internet" -Direction Inbound -Protocol TCP -LocalPort 2375 -RemoteAddress Internet -Action BlockMonitor port 2375
Run a TCP port monitor against your public IP on port 2375: here, a failed connection is the healthy result, so you know the firewall is still doing its job. On Linux, the Statance agent also reports every listening port on the server. TCP port monitoring.
Related ports
| Port 2376 | Docker Engine API (TLS) | High risk |
| Port 6443 | Kubernetes API server | High risk |
| Port 10250 | Kubernetes kubelet API | Critical risk |
FAQ
Is it safe to expose the Docker daemon on port 2375?
No. Access to the Docker API is equivalent to root on the host, and port 2375 has no authentication or encryption. Use SSH or TLS-protected 2376 instead.
What is port 2375 used for?
Port 2375 is the Docker daemon’s remote API without TLS. It is only open if dockerd has been started with -H tcp://0.0.0.0:2375 or the equivalent setting.
Is port 2375 TCP or UDP?
Docker Engine API (unencrypted) uses TCP on port 2375.
How do I check if port 2375 is open?
On the server, run sudo ss -tulpn | grep ':2375 ' (Linux) or Get-NetTCPConnection -LocalPort 2375 (Windows) to see what is listening. From another machine, run nc -zv HOST 2375 or Test-NetConnection HOST -Port 2375.
Know the moment a port stops answering.
TCP, HTTP, DNS and SSL checks from six regions, plus server metrics from a one-line agent.