Port 3300Ceph Monitor

Ceph monitor traffic using the Ceph Messenger v2 protocol, normally listening on TCP port 3300.

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

also known as Ceph msgr2, Ceph monitor service

1 other service is registered on port 3300. compare all 2 →

Technical Details

what runs on :3300

Ceph Monitor traffic on TCP/3300 uses Ceph Messenger v2, a binary protocol with an initial connection preamble and banner, session negotiation, authentication, and framed messages. CephX authentication is normally used, while Messenger integrity checking or encryption depends on the configured mode; the usual default is CRC integrity rather than encryption. Port 6789 is the traditional Ceph Messenger v1 monitor port, and a cluster may expose both versions.

Security Information

exposure of :3300

risk score

8/ 10risk

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

system averages 3.0 across 578 ports — this one sits 5.0 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

Ceph monitors are cluster control-plane services and should normally be reachable only from trusted cluster and client networks, not from the public internet. Exposure can permit reconnaissance, resource exhaustion, exploitation of monitor or messenger vulnerabilities, and—if authentication or configuration is weak—access to sensitive cluster metadata or operations. Use CephX, restrict source networks with firewalls, and configure Messenger secure mode when confidentiality is required.

Record

iana registry entry

port: :3300
service: Ceph Monitor
transport: TCP
encryption: cleartext
assignment: iana registered
risk: 8/10risk
category: System Cloud
usage: TCP port 3300 is the standard Ceph monitor endpoint for the Messenger v2 protocol. Ceph clients and daemons such as OSDs and MDS servers use it to reach monitor services; older Messenger v1 deployments commonly use port 6789.
lookups: 0rank 994
added: 2026-08-30
updated: 2026-08-30
references: IANA service name registry — port 3300

Something wrong?

This record is maintained by the engineers who use port 3300. 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-08-30.

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 578 in system →

the 8 most looked-up other ports in system — 578 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 :3300Ceph Monitor

Technical Details

Security Information

Related Ports

Port 3300Ceph Monitor