Port 2379etcd

etcd client API traffic, used by clients and control planes to read and modify distributed key-value data.

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

also known as etcd-client, etcd client API, port 2379

Technical Details

what runs on :2379

etcd v3 clients normally use gRPC over HTTP/2 with Protocol Buffers on TCP 2379; the v2 API used HTTP/1.1 and JSON, and HTTP/JSON gateways may also be configured. TLS is enabled with certificate-related listen and client-cert flags rather than being inherent to the port, so a default or development deployment may use plaintext. The separate etcd peer endpoint normally listens on TCP 2380 for cluster replication traffic.

Security Information

exposure of :2379

risk score

8/ 10risk

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

databases averages 3.2 across 124 ports — this one sits 4.8 above.

in transit

cleartext

credentials and payloads are readable by anyone on path

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 endpoint should not be exposed directly to the public internet. An unauthenticated or weakly protected client endpoint can allow attackers to read, modify, or delete key-value data and, in Kubernetes environments, potentially access or alter sensitive cluster state and secrets. Use TLS, client authentication, etcd authorization, network controls, and restrict access to trusted clients.

Record

iana registry entry

port: :2379
service: etcd
transport: TCP
encryption: cleartext
assignment: iana registered
risk: 8/10risk
category: Databases System
usage: Port 2379 is the client endpoint for etcd, commonly used by Kubernetes control planes and other distributed systems. It accepts client API requests, while etcd peer-to-peer traffic normally uses TCP port 2380.
lookups: 0rank 994
added: 2026-09-22
updated: 2026-09-22
references: IANA service name registry — port 2379

Something wrong?

This record is maintained by the engineers who use port 2379. 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 124 in databases →

the 8 most looked-up other ports in databases — 124 ports carry that label.

port	service	proto	category	risk	views
:8882	Atlasz Secure App Server	TCP	Web Services	caution	66.9k
:9001	ETL Service Manager	TCPUDP	Databases	caution	28.6k
:2484	Oracle SSL Listener	TCPUDPtls	Security	caution	25.0k
:5495	Applix TM1 Admin	TCP	Databases	caution	24.8k
:591	FileMaker Web Sharing	TCP	Web Services	caution	23.1k
:1521	Oracle TNS Listener	TCP	Security	caution	19.6k
:21001	AMLFilter Admin	TCP	Security	caution	19.2k
:18206	Audition FAM DB	TCPUDP	Databases	caution	19.1k

risk mix of the 8 listed

caution100%

1 of 8 encrypted

Port :2379etcd

Technical Details

Security Information

Related Ports

Port 2379etcd