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