Port 2376 is the Docker daemon’s remote API protected with TLS. With --tlsverify, only clients holding a certificate signed by your CA can connect. It should not be reachable from the public internet.
- Port
- 2376
- Protocol
- TCP
- Service
- Docker Engine API (TLS)
- Expose to internet?
- No
Is port 2376 safe to open?
With mutual TLS correctly configured, unauthenticated users cannot use the API. But any client certificate holder has root-equivalent control of the host, and a daemon started with TLS but without --tlsverify accepts any client. Treat the client certificates like root passwords.
How to secure Docker Engine API (TLS)
- Run dockerd with
--tlsverify,--tlscacert,--tlscertand--tlskey. - Issue client certificates only to people and systems that need root on the host, and rotate them.
- Restrict 2376 to known IP addresses.
- Consider SSH (
DOCKER_HOST=ssh://) instead, which reuses existing SSH access controls.
Check if port 2376 is open
Linux: what is listening on this port
sudo ss -tlpn | grep ':2376 'Windows (PowerShell): what is listening
Get-NetTCPConnection -LocalPort 2376 -State Listen | Select-Object LocalAddress, OwningProcess, @{n='Process';e={(Get-Process -Id $_.OwningProcess).Name}}From another machine: is it reachable
nc -zv HOST 2376
# or
nmap -p 2376 HOST
# Windows
Test-NetConnection HOST -Port 2376Restrict port 2376 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:2376:2376) 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 2376 proto tcp
sudo ufw deny 2376/tcpfirewalld: allow one source network only
sudo firewall-cmd --permanent --remove-port=2376/tcp
sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="10.0.0.0/8" port port="2376" protocol="tcp" accept'
sudo firewall-cmd --reloadiptables
sudo iptables -A INPUT -p tcp --dport 2376 -s 10.0.0.0/8 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 2376 -j DROPWindows Firewall (PowerShell, as Administrator)
New-NetFirewallRule -DisplayName "Block 2376 from internet" -Direction Inbound -Protocol TCP -LocalPort 2376 -RemoteAddress Internet -Action BlockMonitor port 2376
Run a TCP port monitor against your public IP on port 2376: 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 2375 | Docker Engine API (unencrypted) | Critical risk |
| Port 6443 | Kubernetes API server | High risk |
| Port 22 | SSH | Medium risk |
FAQ
What is port 2376 used for?
Port 2376 is the Docker daemon’s remote API protected with TLS. With --tlsverify, only clients holding a certificate signed by your CA can connect.
Is it safe to open port 2376?
Not to the public internet. With mutual TLS correctly configured, unauthenticated users cannot use the API. But any client certificate holder has root-equivalent control of the host, and a daemon started with TLS but without --tlsverify accepts any client. Treat the client certificates like root passwords.
Is port 2376 TCP or UDP?
Docker Engine API (TLS) uses TCP on port 2376.
How do I check if port 2376 is open?
On the server, run sudo ss -tulpn | grep ':2376 ' (Linux) or Get-NetTCPConnection -LocalPort 2376 (Windows) to see what is listening. From another machine, run nc -zv HOST 2376 or Test-NetConnection HOST -Port 2376.
Know the moment a port stops answering.
TCP, HTTP, DNS and SSL checks from six regions, plus server metrics from a one-line agent.