Port 20670Track
TCP/UDP 20670 is registered as Track to Michael Sweet, but no common public listener or documented protocol is established.
- 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,396 · top 16%
Technical Details
what runs on :20670Track is registered on port :20670 over tcp and udp to Michael Sweet. 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 :20670
# linux
sudo ss -tulpn 'sport = :20670'
# macos / bsd
sudo lsof -nP -i :20670
# windows (then: tasklist /FI "PID eq <pid>")
netstat -ano | findstr :20670nmap -sV -p T:20670 <host>
sudo nmap -sU -sV -p U:20670 <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 :20670risk 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 :20670 yet
known exploits, hardening advice, what a compromise looks like — suggest an edit if you know its exposure.
Related Ports
ports registered around :20670, by lookups.
| port | service | risk | |||
|---|---|---|---|---|---|
| :20720 | Symantec i3 Web GUI | TCP | Web Services | caution | 5.6k |
risk mix of the 1 listed
- caution100%
0 of 1 encrypted