Port 2377Docker Swarm

Docker Swarm cluster management traffic between managers and nodes, including control-plane and consensus communication.

transport
tcp

single transport

in transit
encrypted

payload protected on the wire

assignment
official

registered with iana

risk
8/10

risk

lookups
0

rank 994 of 4,021 · top 25%

also known as Docker Swarm manager, 2377/tcp

Technical Details

what runs on :2377

Docker Swarm uses TCP 2377 for its manager control plane, implemented by SwarmKit with gRPC over TLS. Normal deployments use mutually authenticated TLS with certificates issued by the Swarm CA, providing encrypted and authenticated node-to-manager communication. TCP/UDP 7946 carries node discovery and gossip, UDP 4789 carries encrypted overlay-network data, and Docker's separate API ports are typically 2375 (unencrypted) or 2376 (TLS).

Security Information

exposure of :2377

risk score

8/ 10risk

treat as sensitive. widely scanned and regularly exploited when reachable — restrict it to known sources.

cloud averages 4.1 across 109 ports — this one sits 3.9 above.

in transit

encrypted

payloads are protected on the wire

assignment

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp

every listening transport is another surface to filter at the edge

security overview

This port should not be exposed directly to the public internet. A reachable Swarm manager control plane presents a high-value administrative target; possession or compromise of valid Swarm client certificates can enable cluster management, while vulnerabilities in the Docker Engine or SwarmKit could provide a path to broader host or workload compromise. Restrict it to trusted cluster networks and protect the Swarm CA and node certificates.

the 8 most looked-up other ports in cloud — 109 ports carry that label.

risk mix of the 8 listed

  • caution100%

0 of 8 encrypted