Port 32768FileNet TMS
FileNet TMS uses TCP and UDP port 32768 for its application traffic.
- 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 4,759 · top 21%
Technical Details
what runs on :32768FileNet TMS is registered on port :32768 over tcp and udp to Daniel Whelan. 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 sometimes. What's listening is often not the registered service, so check before you assume.
find what's listening on :32768
# linux
sudo ss -tulpn 'sport = :32768'
# macos / bsd
sudo lsof -nP -i :32768
# windows (then: tasklist /FI "PID eq <pid>")
netstat -ano | findstr :32768nmap -sV -p T:32768 <host>
sudo nmap -sU -sV -p U:32768 <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 :32768risk 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 :32768 yet
known exploits, hardening advice, what a compromise looks like — suggest an edit if you know its exposure.
Related Ports
ports registered around :32768, by lookups.
| port | service | risk | |||
|---|---|---|---|---|---|
| :32769 | FileNet RPC | TCP | File Transfer | caution | 9.5k |
| :32767 | FileNet BPM WS-ReliableMessaging Client | TCPUDP | Web Services | safe | 0 |
risk mix of the 2 listed
- safe50%
- caution50%
0 of 2 encrypted