- 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 565: whoami
Port 565 is assigned by IANA to whoami (whoami).
How whoami works
Other servicesThe client sends a request to port 565 and the whoami 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 565 dangerous?
We have no specific security note for port 565. Its risk depends on the program actually listening on it. General advice for other services services:
IANA registry entries for port 565
| Service | Port | Transport | Description | Reference | Updated |
|---|---|---|---|---|---|
| whoami | 565 | TCP, UDP | whoami | - | - |
// source: IANA service name and port number registry
Which program uses port 565, and is it reachable?
Linux
sudo ss -ltnup 'sport = :565' # process listening on 565
sudo lsof -nP -i :565macOS
sudo lsof -nP -i :565
Windows (PowerShell)
Get-NetTCPConnection -LocalPort 565 -State Listen | Select LocalAddress, OwningProcess Get-NetUDPEndpoint -LocalPort 565 netstat -ano | findstr :565
From another machine
nmap -p 565 -sV <host> sudo nmap -sU -p 565 <host> nc -zv <host> 565
Block it in the firewall
sudo ufw deny 565/tcp # Linux (ufw) New-NetFirewallRule -DisplayName "Block 565" -Direction Inbound -LocalPort 565 -Protocol TCP -Action Block # Windows
What is port 565 used for?
Port 565 is assigned by IANA to whoami (whoami).
Is port 565 TCP or UDP?
Port 565 is registered for TCP and UDP.
Is it safe to open port 565?
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 565 is open?
On Linux run "ss -ltnup 'sport = :565'", on macOS "lsof -nP -i :565", and on Windows "netstat -ano | findstr :565" to see the local process. From another machine, "nmap -p 565 <host>" shows whether it is reachable.