Port 1833UDP Radio

UDP Radio service assigned to TCP and UDP port 1833.

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
1/10

safe

lookups
0

rank 993 of 5,592 · top 18%

Technical Details

what runs on :1833

UDP Radio is registered on port :1833 over tcp and udp to Guus Sliepen. We don't have a technical write-up for it beyond the IANA registry entry.

In nmap's internet-wide scan data this port is never observed open, so if it's open on your network it's more likely a custom or misconfigured service than the registered one.

find what's listening on :1833

this machine
# linux
sudo ss -tulpn 'sport = :1833'

# macos / bsd
sudo lsof -nP -i :1833

# windows (then: tasklist /FI "PID eq <pid>")
netstat -ano | findstr :1833
another host
nmap -sV -p T:1833 <host>
sudo nmap -sU -sV -p U:1833 <host>

run it? the handshake, the implementations you meet in the wild and the flags that matter come from the engineers who do.

add technical details

Security Information

exposure of :1833

risk score

1/ 10safe

routine exposure. this port is rarely the way in on its own — keep it patched and logged and move on.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

no security notes recorded for :1833 yet

known exploits, hardening advice, what a compromise looks like — suggest an edit if you know its exposure.

ports registered around :1833, by lookups.

portservicerisk
:1863Microsoft Notification Protocolcaution
:1883MQTT Brokercaution
:1812RADIUS Auth Protocolcaution
:1886Leonardo over IPcaution
:1801MSMQcaution
:1813RADIUS Accountingcaution
:1773KMSControlsafe
:1840Netopia VO2safe

risk mix of the 8 listed

  • safe25%
  • caution75%

0 of 8 encrypted