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