Port 1935Macromedia Flash Communications Server MX

Historical Flash streaming and messaging service, typically using RTMP on port 1935.

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
2/10

safe

lookups
0

rank 994 of 3,803 · top 26%

also known as macromedia-fcs, RTMP, Flash Media Server

1 other service is registered on port 1935. compare all 2

Technical Details

what runs on :1935

The normal protocol is Real-Time Messaging Protocol (RTMP) over TCP port 1935. RTMP begins with a versioned handshake and then exchanges timestamped, chunked messages carrying commands, media, and application data, commonly encoded with AMF. HTTP-tunneled RTMP and TLS-protected variants historically used ports 80 and 443; UDP registration is associated with Flash media-server protocol support but is not the usual transport for classic RTMP.

Security Information

exposure of :1935

risk score

2/ 10safe

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

streaming averages 3.1 across 45 ports — this one sits 1.1 below.

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

Classic RTMP is not encrypted by default, so media and application traffic can be observed or manipulated in transit. Legacy deployments should not be exposed directly to the internet without authentication, patching, and strict application controls; however, this assignment appears obsolete and was never observed open in the cited scan data.

the 8 most looked-up other ports in streaming — 45 ports carry that label.

risk mix of the 8 listed

  • safe13%
  • caution88%

0 of 8 encrypted