Port 2375 (Docker API (plain))

Docker Engine remote API without TLS, enabled with dockerd -H tcp://0.0.0.0:2375.

Registered (user) port, 1024-49151 TCP Containers and Kubernetes Do not expose to the internet

What port 2375 is used for

Docker Engine remote API without TLS, enabled with dockerd -H tcp://0.0.0.0:2375.

Security: should port 2375 be open?

Do not expose to the internet. Exposing 2375 gives anyone root on the host: they can start a privileged container that mounts /. Cryptomining worms scan for it constantly. Use the local Unix socket, SSH (docker -H ssh://), or 2376 with client certificates.

IANA assignment

Service nameProtoDescriptionAssigneeReference

docker TCP Docker REST API (plain text) DOCKER -

Registry dates for this port: registered 2014-04-17.

Check what is listening on port 2375

Linux: is anything listening on TCP 2375?

sudo ss -tlnp 'sport = :2375'

Linux / macOS: which process owns the port

sudo lsof -nP -i :2375

Older Linux / BSD (net-tools)

sudo netstat -tlnp | grep ':2375 '

Windows (Command Prompt)

netstat -ano | findstr :2375

Windows (PowerShell)

Get-NetTCPConnection -LocalPort 2375 -State Listen | Select LocalAddress,OwningProcess

Test it from outside

From another machine

nc -vz -w 5 HOST 2375

From Windows

Test-NetConnection HOST -Port 2375

Block port 2375 in the firewall

ufw

sudo ufw deny 2375/tcp

iptables

sudo iptables -A INPUT -p tcp --dport 2375 -j DROP

nftables

sudo nft add rule inet filter input tcp dport 2375 drop

Windows Firewall

New-NetFirewallRule -DisplayName 'Block TCP 2375' -Direction Inbound -Protocol TCP -LocalPort 2375 -Action Block

All port numbers · Open port checker
Assignment data: IANA port number registry (public domain), retrieved 2026-11-10.