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