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