Port 5968MPP Policy v5

MPP Policy v5 traffic uses TCP or UDP port 5968.

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,727 · top 21%

also known as mppolicy-v5

Technical Details

what runs on :5968

MPP Policy v5 is registered on port :5968 over tcp and udp to Yutaka Ono. 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 :5968

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

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

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

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

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

ports registered around :5968, by lookups.

portservicerisk
:5938TeamViewercaution
:6005BMC Control-M Servercaution
:6005Camfrog Chatcaution
:6000X11 Protocolcaution
:6001X11 Display Managercaution
:5912Tidal Scheduler Agentcaution
:5984CouchDBcaution
:5999CVSupcaution

risk mix of the 8 listed

  • caution100%

0 of 8 encrypted