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