Port 357bhevent

The bhevent service is assigned to TCP and UDP port 357, but no public protocol details are recorded.

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 5,426 · top 18%

Technical Details

what runs on :357

bhevent is registered on port :357 over tcp and udp to John Kelly. 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 :357

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

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

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

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

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

ports registered around :357, by lookups.

risk mix of the 8 listed

  • caution100%

0 of 8 encrypted