Port 3595ShareApp

An obscure ShareApp service assigned to TCP and UDP port 3595.

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,216 · top 24%

Technical Details

what runs on :3595

ShareApp is registered on port :3595 over tcp and udp to Jeff King, assigned September 2002. 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 :3595

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

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

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

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

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

ports registered around :3595, by lookups.

risk mix of the 8 listed

  • safe13%
  • caution88%

0 of 8 encrypted