Port 2376Docker Remote API (TLS)

TLS-secured Docker Engine API used by remote clients and automation to manage containers, images, networks, and volumes.

inSystem Virtualization

transport: tcp
in transit: encrypted
assignment: official
risk: 8/10
lookups: 0

also known as docker-s, Docker API over TLS, Docker TLS API

Technical Details

what runs on :2376

The service runs over TCP with a TLS handshake, normally using mutual certificate authentication, followed by Docker Engine's HTTP/1.1 REST API. Requests and responses commonly use JSON, while container attach, exec, logs, and similar operations can use upgraded or streaming HTTP connections. Docker daemons normally use the local Unix socket; TCP 2376 is the conventional TLS-protected remote API port, while 2375 conventionally denotes the unencrypted remote API.

Security Information

exposure of :2376

risk score

8/ 10risk

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

system averages 2.5 across 903 ports — this one sits 5.5 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 is a high-impact administrative interface: a client that can authenticate to it can commonly control containers and potentially obtain host-level access through mounted filesystems, privileged containers, or the Docker socket. It should not be exposed directly to the public internet; restrict it with network controls and strong mutual TLS credentials, and treat client certificates as equivalent to administrative secrets.

Record

iana registry entry

port: :2376
service: Docker Remote API (TLS)
transport: TCP
encryption: tls / encrypted
assignment: iana registered
risk: 8/10risk
category: System Virtualization
usage: Docker Engine exposes its remote REST API over TCP 2376 when TLS is enabled. Docker CLI clients, orchestration tools, and CI/CD automation may connect here to manage containers, images, networks, and volumes; the local Unix socket and unencrypted remote API conventionally use different endpoints.
lookups: 0rank 994
added: 2026-09-22
updated: 2026-09-22
references: IANA service name registry — port 2376

Something wrong?

This record is maintained by the engineers who use port 2376. Every field on it is editable — change what's wrong, say how you know, and a reviewer publishes it, usually within a minute. Last touched 2026-09-22.

01edit any field on a page of its own
02a model checks it for accuracy and spam
03clean and confident goes live immediately

edit this record →back to the registry

Related Ports

all 903 in system →

the 8 most looked-up other ports in system — 903 ports carry that label.

port	service	proto	category	risk	views
:8888	Sun Answerbook & Alt HTTP	TCP	Web Services	caution	123.9k
:4664	Google Desktop Search	TCP	System	caution	67.2k
:8008	IBM HTTP Server Admin	TCP	Web Services	caution	58.3k
:3268	Microsoft Global Catalog (GC)	TCPUDP	Security	caution	54.6k
:135	Microsoft EPMAP	TCPUDP	Security	caution	51.9k
:9080	WebSphere HTTP Transport (default)	TCP	Web Services	caution	51.6k
:23	Telnet	TCP	Remote Access	caution	34.8k
:12489	NSClient Monitoring Agent	TCP	Network Services	caution	30.0k

risk mix of the 8 listed

caution100%

0 of 8 encrypted

Port :2376Docker Remote API (TLS)

Technical Details

Security Information

Related Ports

Port 2376Docker Remote API (TLS)