whatportis.com
suggest an edit →

Port 1935RTMP

The Real Time Messaging Protocol (RTMP) is a proprietary protocol developed by Macromedia, now owned by Adobe, primarily used for high-performance transmission of audio, video, and data between a server and Flash player. Operating over TCP port 1935, RTMP enables low-latency streaming which contributed to Flash's dominance in web video delivery during its peak. Despite Flash's decline, RTMP remains popular in live streaming infrastructure and content delivery due to its robustness, simplicity, and widespread support..

inWeb ServicesStreamingMedia
transport
tcp

single transport

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
2/10

safe

lookups
11,075

rank 384 of 993 · top 39%

Technical Details

what runs on :1935

RTMP (Real Time Messaging Protocol) is designed to facilitate real-time communication between streaming servers and clients. It leverages a persistent TCP connection which allows the continuous exchange of audio, video, and data streams. Because of this persistent connection, RTMP enables low-latency communication suitable for live broadcast scenarios.

RTMP originally served Adobe Flash Player, carrying multimedia content encoded in formats like MP3 or AAC for audio and H.264 for video. The protocol supports packet fragmentation and multiplexing multiple streams within a single connection, enhancing efficiency and enabling features such as streaming while recording and adaptive bitrate streaming (via various RTMP flavors).

While Flash Player adoption has waned, RTMP is still widely used in streaming workflows, especially as an ingest protocol from encoders to servers like Wowza or media platforms, before content is transcoded and delivered via modern, HTTP-based protocols such as HLS or DASH. RTMP supports both encrypted and unencrypted variants, though the plain protocol on port 1935 typically lacks encryption.

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.

web services averages 3.9 across 112 ports — this one sits 1.9 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

every listening transport is another surface to filter at the edge

security overview

Common Vulnerabilities:
- Lack of encryption in the plain RTMP protocol can expose transmitted content and metadata to eavesdropping or data interception.
- Authentication may be weak or absent, making the service susceptible to unauthorized streaming (stream hijacking) or malicious data injection.
- Flash-based client implementations have historically introduced vulnerabilities like buffer overflows and cross-protocol exploits.

Common Mitigations:
- Employ encrypted variants of RTMP such as RTMPS (over TLS/SSL) to safeguard data in transit.
- Implement strong access controls and authentication, including token-based mechanisms to restrict stream publishing and subscription.
- Use firewalls to restrict source IP ranges and limit exposure to public networks.
- Monitor and log streaming connections, and patch associated server software to protect against exploits targeting protocol implementations or related services.

Related Ports

all 112 in web services →

the 8 most looked-up other ports in web services — 112 ports carry that label.

portservicerisk
:8888Sun Answerbook & Alt HTTPcaution
:8000Intel Remote Desktop / Alternate HTTP Portsafe
:8888NewsEDGEcaution
:8888HTTP Alternative Portcaution
:8888GNUmp3d Streaming HTTPcaution
:9080Groove RPCcaution
:8881Atlasz Secure Servercaution
:80HTTPcaution

risk mix of the 8 listed

  • safe13%
  • caution88%

0 of 8 encrypted