Port 5112PeerMe Message Command Service

Port 5112 is assigned to PeerMe message commands; public documentation of its protocol and deployments is not available.

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

also known as pm-cmdsvr

Technical Details

what runs on :5112

PeerMe Message Command Service is registered on port :5112 over tcp and udp to Marcos Della, assigned August 2005. We don't have a technical write-up for it beyond the IANA registry entry.

In nmap's internet-wide scan data this port is never observed open, so if it's open on your network it's more likely a custom or misconfigured service than the registered one.

find what's listening on :5112

this machine

# linux
sudo ss -tulpn 'sport = :5112'

# macos / bsd
sudo lsof -nP -i :5112

# windows (then: tasklist /FI "PID eq <pid>")
netstat -ano | findstr :5112

another host

nmap -sV -p T:5112 <host>
sudo nmap -sU -sV -p U:5112 <host>

run it? the handshake, the implementations you meet in the wild and the flags that matter come from the engineers who do.

add technical details

Security Information

exposure of :5112

risk score

1/ 10safe

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

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

no security notes recorded for :5112 yet

known exploits, hardening advice, what a compromise looks like — suggest an edit if you know its exposure.

Record

iana registry entry

port: :5112
service: PeerMe Message Command Service
transport: TCPUDP
encryption: cleartext
assignment: iana registered
risk: 1/10safe
category: uncategorised
usage: The IANA entry identifies this as the PeerMe Msg Cmd Service and lists Marcos Della as the registrant. No established public documentation identifies implementations or routine deployments.
lookups: 0rank 993
added: 2026-10-07
updated: 2026-10-07
references: IANA service name registry — port 5112

Something wrong?

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

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

browse categories →

ports registered around :5112, by lookups.

port	service	proto	category	risk	views
:5104	IBM Netcool Impact HTTP	TCP	Network Services	caution	22.2k
:5070	BFCP	TCP	Network Services	caution	15.2k
:5061	SIP over TLS	TCP	Security	caution	14.4k
:5093	SafeNet License Manager	UDP	System	caution	13.3k
:5107	A-Talk Remote Server	TCP	Remote Access	caution	12.2k
:5060	SIP	TCPUDP	Network Services	caution	11.4k
:5106	A-Talk	TCP	Voice and Chat	caution	11.1k
:5099	SafeNet Sentinel License Manager	TCPUDP	System	caution	10.8k

risk mix of the 8 listed

caution100%

0 of 8 encrypted

Port :5112PeerMe Message Command Service

Technical Details

Security Information

Related Ports

Port 5112PeerMe Message Command Service