Port 4487Protocol for Remote Execution

Port 4487 is assigned to a TCP protocol for remote execution.

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

also known as prex-tcp

Technical Details

what runs on :4487

Protocol for Remote Execution is registered on port :4487 over tcp to Daniel Ruppert, assigned September 2010. 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 :4487

this machine

# linux
sudo ss -tlpn 'sport = :4487'

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

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

another host

nmap -sV -p T:4487 <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 :4487

risk score

1/ 10safe

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

remote access averages 3.8 across 207 ports — this one sits 2.8 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

every listening transport is another surface to filter at the edge

security overview

no security notes recorded for :4487 yet

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

Record

iana registry entry

port: :4487
service: Protocol for Remote Execution
transport: TCP
encryption: cleartext
assignment: iana registered
risk: 1/10safe
category: Remote Access
usage: IANA assigns TCP port 4487 to a protocol for remote execution, registered to Daniel Ruppert. There is no established common deployment or implementation to identify from the available information.
lookups: 0rank 993
added: 2026-10-05
updated: 2026-10-05
references: IANA service name registry — port 4487

Something wrong?

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

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

the 8 most looked-up other ports in remote access — 207 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 :4487Protocol for Remote Execution

Technical Details

Security Information

Related Ports

Port 4487Protocol for Remote Execution