- Close the port if nothing on the host needs it.
- Identify the process that listens on it (commands below) before opening it in a firewall.
- Expose a service only to the networks that use it.
Port 357: bhevent
Port 357 is assigned by IANA to bhevent (bhevent).
How bhevent works
Other servicesThe client sends a request to port 357 and the bhevent service answers.
- Transport
- TCP · UDP
- Exposure risk
- not rated depends on the program listening
- Encryption
- Unknownnot stated by the registry
- IANA status
- Assigned1 registered service
- Range
- Well-known (0-1023)
- Category
- Other services
Is port 357 dangerous?
We have no specific security note for port 357. Its risk depends on the program actually listening on it. General advice for other services services:
IANA registry entries for port 357
| Service | Port | Transport | Description | Reference | Updated |
|---|---|---|---|---|---|
| bhevent | 357 | TCP, UDP | bhevent | - | - |
// source: IANA service name and port number registry
Which program uses port 357, and is it reachable?
Linux
sudo ss -ltnup 'sport = :357' # process listening on 357
sudo lsof -nP -i :357macOS
sudo lsof -nP -i :357
Windows (PowerShell)
Get-NetTCPConnection -LocalPort 357 -State Listen | Select LocalAddress, OwningProcess Get-NetUDPEndpoint -LocalPort 357 netstat -ano | findstr :357
From another machine
nmap -p 357 -sV <host> sudo nmap -sU -p 357 <host> nc -zv <host> 357
Block it in the firewall
sudo ufw deny 357/tcp # Linux (ufw) New-NetFirewallRule -DisplayName "Block 357" -Direction Inbound -LocalPort 357 -Protocol TCP -Action Block # Windows
What is port 357 used for?
Port 357 is assigned by IANA to bhevent (bhevent).
Is port 357 TCP or UDP?
Port 357 is registered for TCP and UDP.
Is it safe to open port 357?
It depends on the program that listens on it. Open it only for a service you know and only to the networks that need it. Close the port if nothing on the host needs it.
How do I check if port 357 is open?
On Linux run "ss -ltnup 'sport = :357'", on macOS "lsof -nP -i :357", and on Windows "netstat -ano | findstr :357" to see the local process. From another machine, "nmap -p 357 <host>" shows whether it is reachable.