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