Port 4379CTDB (Clustered TDB)

CTDB uses this port for node communication in clustered Samba and Linux file-server deployments.

transport: tcp · udp
in transit: cleartext
assignment: official
risk: 5/10
lookups: 0

Technical Details

what runs on :4379

CTDB nodes use port 4379 for cluster communication, with the service registered for both TCP and UDP. The CTDB protocol is a binary control protocol, not a browser-facing service or an ordinary TLS endpoint; node addresses and cluster membership are configured by the deployment. It is normally permitted only between cluster members on dedicated or otherwise restricted network interfaces.

Security Information

exposure of :4379

risk score

5/ 10caution

worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.

network services averages 2.6 across 1,534 ports — this one sits 2.4 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 · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

Do not expose CTDB to the public internet. It is a cluster control-plane service intended for trusted peers, and traffic is not encrypted by default; restrict access to the cluster nodes and use network isolation rather than assuming the protocol provides transport security.

Record

iana registry entry

port: :4379
service: CTDB (Clustered TDB)
transport: TCPUDP
encryption: cleartext
assignment: iana registered
risk: 5/10caution
category: Network Services System
usage: CTDB is a clustered database and node-coordination service commonly deployed with Samba to support clustered file servers. Engineers are most likely to encounter it on the private network between members of a CTDB cluster, rather than on a public-facing host.
lookups: 0rank 993
added: 2026-10-04
updated: 2026-10-04
references: IANA service name registry — port 4379

Something wrong?

This record is maintained by the engineers who use port 4379. 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-10-04.

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 1,534 in network services →

the 8 most looked-up other ports in network services — 1,534 ports carry that label.

port	service	proto	category	risk	views
:9080	Groove RPC	TCPUDP	Web Services	caution	70.8k
:6543	Jetnet	UDP	Network Services	caution	65.3k
:5938	TeamViewer	TCPUDP	Remote Access	caution	65.0k
:8291	Winbox MikroTik Admin	TCP	Security	caution	62.9k
:3233	WhiskerControl Protocol	TCPUDP	Network Services	caution	61.9k
:3268	Microsoft Global Catalog (GC)	TCPUDP	Security	caution	54.6k
:135	Microsoft EPMAP	TCPUDP	Security	caution	51.9k
:3128	Tatsoft Default HTTP Proxy	TCP	Web Services	caution	46.8k

risk mix of the 8 listed

caution100%

0 of 8 encrypted

Port :4379CTDB (Clustered TDB)

Technical Details

Security Information

Related Ports

Port 4379CTDB (Clustered TDB)