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