Port 26260eZproxy

Port 26260 is registered for eZproxy, but no common deployment or scan-observed listener is established.

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
1/10

safe

lookups
0

rank 993 of 6,483 · top 15%

Technical Details

what runs on :26260

eZproxy is registered on port :26260 over tcp and udp to Albert C Yang. 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 :26260

this machine
# linux
sudo ss -tulpn 'sport = :26260'

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

# windows (then: tasklist /FI "PID eq <pid>")
netstat -ano | findstr :26260
another host
nmap -sV -p T:26260 <host>
sudo nmap -sU -sV -p U:26260 <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 :26260

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 :26260 yet

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

ports registered around :26260, by lookups.

portservicerisk
:26208wnn6-dssafe
:26257CockroachDBrisk
:26261eZmeetingsafe
:26262K3 Software-Serversafe
:26263K3 Software-Clientsafe

risk mix of the 5 listed

  • safe80%
  • risk20%

1 of 5 encrypted