Port 2375 (Docker API) — What It Is and How to Use It

Port 2375 is commonly used for the Docker Remote API, allowing external clients to interact with the Docker daemon. It enables programmatic control over Docker containers, images, networks, and volumes, making it crucial for automation and remote management of Docker environments.

Last updated: 2026-06-11

RECOMMENDED

Gear Up: Mechanical Keyboards for Developers

Reduce fatigue and type faster with premium mechanical keyboards. Check out top picks for software engineers.

Shop Developer Gear →
Port Number 2375
Protocol Docker API

Common Use Cases

  • Remote management of Docker hosts (e.g., starting/stopping containers, building images)
  • Integration with CI/CD pipelines for automated container deployments
  • Monitoring and orchestration tools interacting with Docker daemons
  • Development environments where a local client controls a remote Docker engine

Interactive Command Builder

nc -zv example.com 2375

Check if Port 2375 is Open

sudo netstat -tulnp | grep 2375
netstat -ano | findstr :2375
⚠️ Security Note: Leaving port 2375 open without proper authentication and encryption is a significant security risk, as it grants full control over the Docker daemon. It should only be exposed over a secure, encrypted channel (like TLS) and with strong authentication mechanisms.

Related Ports

Frequently Asked Questions

Is port 2375 dangerous to leave open?

Yes, absolutely. Exposing port 2375 without TLS encryption and authentication is extremely dangerous as it provides unauthenticated root access to the Docker host, allowing anyone to execute arbitrary commands and compromise the system.

What service uses port 2375?

Port 2375 is used by the Docker daemon for its unencrypted HTTP API. It's the default port for the Docker Remote API when not using TLS.