Port 33060MySQL X Protocol

MySQL X Protocol traffic for MySQL’s document-store and SQL APIs, normally served by the X Plugin on TCP port 33060.

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

also known as MySQL X Plugin, X DevAPI

Technical Details

what runs on :33060

This is the MySQL X Protocol over TCP, commonly configured on port 33060. Unlike the classic MySQL protocol on 3306, it uses Protocol Buffers messages framed with a four-byte length followed by a message type and payload. Clients exchange capability and authentication messages before issuing SQL or document-store CRUD operations. The X Plugin supports TLS; its default SSL mode is REQUIRED, though configuration can change that.

Security Information

exposure of :33060

risk score

8/ 10risk

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

databases averages 3.8 across 173 ports — this one sits 4.2 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 database access endpoint: authenticated clients may be able to read or modify data according to their MySQL privileges. Avoid exposing it directly to the internet; restrict access to trusted networks, use least-privilege accounts, keep MySQL patched, and verify that TLS and strong authentication are in use. TLS is supported and normally required by the X Plugin, but server configuration can alter this.

Record

iana registry entry

port: :33060
service: MySQL X Protocol
transport: TCP
encryption: tls / encrypted
assignment: iana registered
risk: 8/10risk
category: Databases
usage: MySQL Server’s X Plugin listens here for clients using the X Protocol, including MySQL Shell and X DevAPI connectors. It is used for document-store CRUD operations and SQL access; Oracle holds the IANA assignment, and the port is distinct from the classic MySQL port 3306.
lookups: 0rank 993
added: 2026-10-20
updated: 2026-10-20
references: IANA service name registry — port 33060

Something wrong?

This record is maintained by the engineers who use port 33060. 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-20.

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 173 in databases →

the 8 most looked-up other ports in databases — 173 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 :33060MySQL X Protocol

Technical Details

Security Information

Related Ports

Port 33060MySQL X Protocol