Port 12012Vipera Messaging Service

Port 12012 is assigned to the Vipera Messaging Service on TCP and UDP.

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

2 other services are registered on port 12012. compare all 3 →

Technical Details

what runs on :12012

Vipera Messaging Service is registered on port :12012 over tcp and udp to Silvano Maffeis 2, assigned August 2005. 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 :12012

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

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

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

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

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

ports registered around :12012, by lookups.

risk mix of the 8 listed

  • safe25%
  • caution75%

0 of 8 encrypted