Port 8384Syncthing GUI (TCP)

TCP 8384 commonly serves Syncthing’s web GUI; UDP 8384 is assigned to the Marathon Transport Protocol.

transport
udp

single transport

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
7/10

risk

lookups
0

rank 993 of 6,034 · top 16%

also known as marathontp, Marathon Transport Protocol

Technical Details

what runs on :8384

The IANA assignment is for UDP and names the Marathon Transport Protocol; its handshake, framing, and deployment behavior are not well documented. Separately, Syncthing commonly listens on TCP 8384 for its HTTP-based web GUI, normally bound to 127.0.0.1:8384 by default. The GUI can be configured to listen on other addresses and to use HTTPS. Syncthing's file synchronization and local discovery use other ports, not this GUI port.

Security Information

exposure of :8384

risk score

7/ 10risk

treat as sensitive. widely scanned and regularly exploited when reachable — restrict it to known sources.

file transfer averages 3.3 across 201 ports — this one sits 3.7 above.

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

udp

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

security overview

The UDP assignment has no established public exposure profile. For TCP 8384, exposing the Syncthing GUI to the internet can grant access to administrative settings and synced-device configuration; the default localhost binding limits network exposure, but a deliberately external listener should have GUI authentication enabled and HTTPS configured. Do not assume an open UDP 8384 socket is Syncthing—the common Syncthing use is TCP.

the 8 most looked-up other ports in file transfer — 201 ports carry that label.

risk mix of the 8 listed

  • caution100%

1 of 8 encrypted