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