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