Port 602XML-RPC over BEEP

XML-RPC calls transported through the Blocks Extensible Exchange Protocol (BEEP), normally over a TCP connection.

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

also known as xmlrpc-beep, BEEP XML-RPC

Technical Details

what runs on :602

BEEP is a connection-oriented, framed protocol that begins with a greeting exchange and uses channels, profiles, and numbered message frames. XML-RPC requests and responses are carried in BEEP message exchanges, with replies and protocol errors represented by BEEP frame types; authentication and TLS can be negotiated through BEEP profiles, but encryption is not inherent. The assignment lists both TCP and UDP, although standard BEEP operation is normally over TCP and does not define a conventional datagram-based mode.

Security Information

exposure of :602

risk score

2/ 10safe

routine exposure. this port is rarely the way in on its own — keep it patched and logged and move on.

web services averages 3.3 across 158 ports — this one sits 1.3 below.

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

XML-RPC over BEEP is not encrypted by default, so credentials and procedure arguments may be exposed unless TLS or another protected transport is used. Internet exposure is unusual and should generally be restricted to trusted peers, with authentication, request validation, rate limiting, and protection against dangerous remotely callable methods.

Record

iana registry entry

port: :602
service: XML-RPC over BEEP
transport: TCPUDP
encryption: cleartext
assignment: iana registered
risk: 2/10safe
category: Web Services Network Services
usage: This port is assigned for applications that expose XML-RPC through BEEP rather than the more common HTTP transport. It is an uncommon, generally legacy or specialized integration protocol; ordinary XML-RPC services typically use HTTP or HTTPS instead.
lookups: 0rank 994
added: 2026-09-10
updated: 2026-09-10
references: IANA service name registry — port 602
RFC 3529

Something wrong?

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

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 158 in web services →

the 8 most looked-up other ports in web services — 158 ports carry that label.

port	service	proto	category	risk	views
:8888	Sun Answerbook & Alt HTTP	TCP	Web Services	caution	123.9k
:8000	Intel Remote Desktop / Alternate HTTP Port	TCP	Web Services	safe	84.3k
:8888	NewsEDGE	TCPUDP	Web Services	caution	83.3k
:8888	HTTP Alternative Port	TCP	Web Services	caution	76.5k
:8888	GNUmp3d Streaming HTTP	TCP	Web Services	caution	76.3k
:9080	Groove RPC	TCPUDP	Web Services	caution	70.8k
:8881	Atlasz Secure Server	TCP	Web Services	caution	67.6k
:80	HTTP	TCPUDP	Web Services	caution	67.3k

risk mix of the 8 listed

safe13%
caution88%

0 of 8 encrypted

Port :602XML-RPC over BEEP

Technical Details

Security Information

Related Ports

Port 602XML-RPC over BEEP