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