Port 2376 — Docker API (TLS)
TCP registered
What runs on port 2376
The Docker daemon API with TLS client certificate authentication.
Security considerations
Still grants full host control to whoever holds a certificate. Treat those certificates like root passwords.
Checking whether something is listening
# Linux / macOS — what is bound to the port
sudo lsof -i :2376
sudo ss -lntp | grep :2376
# Windows
netstat -ano | findstr :2376
Get-NetTCPConnection -LocalPort 2376
# is it reachable from outside?
nc -zv example.com 2376
curl -v telnet://example.com:2376
Freeing the port
# find the process, then stop it
sudo lsof -ti :2376 | xargs kill # Linux / macOS
netstat -ano | findstr :2376 # note the PID, then:
taskkill /PID <pid> /F # Windows
Should this port be open to the internet?
Usually not. Expose it only if a specific external client needs it, and restrict by source address where you can.
Quick reference
| Port | 2376 |
| Protocol | TCP |
| Service | Docker API (TLS) |
| Range | Registered (1024–49151) — any user process may bind |
Frequently asked questions
What is port 2376 used for?
The Docker daemon API with TLS client certificate authentication.
Is it safe to open port 2376?
Still grants full host control to whoever holds a certificate. Treat those certificates like root passwords.
How do I check if port 2376 is open?
Locally, sudo lsof -i :2376 on macOS or Linux, or netstat -ano | findstr :2376 on Windows. From outside, nc -zv host 2376 tells you whether anything answers.
Why do I get "address already in use" on port 2376?
Another process is bound to it — often a previous run of your own program that did not exit cleanly. Find it with lsof -ti :2376 and stop it, or configure your application to use a different port.
Can I change the port this service uses?
Almost always yes, in the service's configuration. Moving off a default port reduces automated scan noise, but it is obfuscation rather than security — a real attacker scans all 65,535.