Port 36001AllPeers Network
An obscure assignment for the AllPeers Network; no common current listener is established on this port.
- transport
- tcp · udp
- in transit
- cleartext
- assignment
- official
- risk
- 1/10
- lookups
- 0
2 transports registered
payload readable on path
registered with iana
safe
rank 993 of 6,572 · top 15%
Technical Details
what runs on :36001AllPeers Network is registered on port :36001 over tcp and udp to Cedric Maloux, assigned April 2007. 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 :36001
# linux
sudo ss -tulpn 'sport = :36001'
# macos / bsd
sudo lsof -nP -i :36001
# windows (then: tasklist /FI "PID eq <pid>")
netstat -ano | findstr :36001nmap -sV -p T:36001 <host>
sudo nmap -sU -sV -p U:36001 <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 detailsSecurity Information
exposure of :36001risk 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 :36001 yet
known exploits, hardening advice, what a compromise looks like — suggest an edit if you know its exposure.
Related Ports
no neighbours mapped to :36001 yet
ports are related through the categories they share — file this one under a category and its neighbours appear here.