Port 16384connected

An obscure TCP/UDP assignment for Connected Corp, with no widely recognized protocol or common listener associated with it.

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,339 · top 16%

1 other service is registered on port 16384. compare all 2 →

Technical Details

what runs on :16384

connected is registered on port :16384 over tcp and udp to Nicole C Ouellette, assigned February 2004. 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 :16384

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

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

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

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

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

ports registered around :16384, by lookups.

risk mix of the 6 listed

  • safe67%
  • caution17%
  • risk17%

0 of 6 encrypted