Port 3121Pacemaker Remote

Pacemaker Remote uses TCP 3121 to let a Pacemaker cluster manage resources on remote nodes.

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

also known as pcmk-remote, pacemaker-remoted

Technical Details

what runs on :3121

The service uses TCP port 3121 and normally begins with a TLS-protected, mutually authenticated connection using Pacemaker authentication credentials, commonly a shared authkey. After the connection is established, the cluster uses the Pacemaker Remote protocol to proxy resource-management operations to the remote node; it is not an interactive SSH service. The port is distinct from Pacemaker administration services such as pcsd, commonly associated with TCP 2224, and from the cluster communication ports used by Corosync.

Security Information

exposure of :3121

risk score

6/ 10risk

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

remote access averages 3.7 across 167 ports — this one sits 2.3 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

Pacemaker Remote provides authenticated remote resource-management access and should be restricted to the cluster nodes or management network with firewall rules. Do not expose TCP 3121 directly to the Internet: compromise of authentication material or the remote daemon could let an attacker execute or control cluster-managed resource operations on the host.

Record

iana registry entry

port: :3121
service: Pacemaker Remote
transport: TCP
encryption: tls / encrypted
assignment: iana registered
risk: 6/10risk
category: Remote Access System
usage: Pacemaker Remote runs the pacemaker-remoted daemon on nodes managed by a Pacemaker high-availability cluster. It extends cluster resource management beyond nodes participating directly in the cluster communication layer, such as virtual machines or remote service hosts.
lookups: 0rank 994
added: 2026-09-12
updated: 2026-09-12
references: IANA service name registry — port 3121

Something wrong?

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

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 167 in remote access →

the 8 most looked-up other ports in remote access — 167 ports carry that label.

port	service	proto	category	risk	views
:8000	Intel Remote Desktop / Alternate HTTP Port	TCP	Web Services	safe	84.3k
:8888	D2GS Admin Console	TCP	Remote Access	caution	83.7k
:8881	Atlasz Secure Server	TCP	Web Services	caution	67.6k
:5938	TeamViewer	TCPUDP	Remote Access	caution	65.0k
:8291	Winbox MikroTik Admin	TCP	Security	caution	62.9k
:8008	IBM HTTP Server Admin	TCP	Web Services	caution	58.3k
:135	Microsoft EPMAP	TCPUDP	Security	caution	51.9k
:23	Telnet	TCP	Remote Access	caution	34.8k

risk mix of the 8 listed

safe13%
caution88%

0 of 8 encrypted

Port :3121Pacemaker Remote

Technical Details

Security Information

Related Ports

Port 3121Pacemaker Remote