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