Port 594TPIP

TPIP uses TCP and UDP port 594; its protocol purpose is not documented in the registry.

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 4,984 · top 20%

Technical Details

what runs on :594

TPIP is registered on port :594 over tcp and udp to Brad Spear. 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 found open rarely. What's listening is often not the registered service, so check before you assume.

find what's listening on :594

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

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

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

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

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

ports registered around :594, by lookups.

portservicerisk
:548Apple Filing Protocolcaution
:593HTTP RPC Endpoint Mappercaution
:591FileMaker Web Sharingcaution
:623ASF-RMCPcaution
:563NNTPSsafe
:546DHCPv6 Clientcaution
:636LDAPScaution
:547DHCPv6 Servercaution

risk mix of the 8 listed

  • safe13%
  • caution88%

2 of 8 encrypted