322

Port 322/tcp is registered with IANA as rtsps, the default port for RTSP-over-TLS session control used by streaming-media systems and IP cameras; it should generally be restricted to trusted networks or a VPN rather than exposed directly to the public internet.

The IANA registry lists the service name rtsps, description "RTSPS," and assignee/contact Anders_Klemets for both 322/tcp and 322/udp identically. The Reference and Registration Date columns are blank in the source registry, so no RFC citation or assignment date can be reported for the IANA record itself.

RFC 7826 (Real-Time Streaming Protocol Version 2.0, December 2016) separately specifies TCP port 322 as the default port for the rtsps:// URI scheme — RTSP wrapped in TLS — when no explicit port is given. This is narrative protocol context, distinct from the registry's own (blank) Reference field.

RTSPS secures the RTSP control and authentication exchange but does not by itself encrypt the media stream unless SRTP is layered on top, per secondary sourcing. Reported common software includes RTSP/RTSPS-capable IP cameras and media servers/toolkits such as FFmpeg, GStreamer, and MediaMTX; most RTSP deployments reportedly still default to unencrypted RTSP on port 554 rather than RTSPS on 322, though no hard adoption statistics were found.

IANA assignment

rtsps — "RTSPS"; assignee/contact Anders_Klemets; Reference field blank; dual-registered 322/tcp + 322/udp identically [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry-656; https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv

IANA Registration Date / Modification Date

blank in the source registry [Confirmed, blank not fabricated] — the IANA Service Name and Transport Protocol Port Number Registry

Range class

registered (256–1023 range within IANA's system ports)

Prevalence

no port-322-specific scan/exposure statistics located in this pass [Unknown] — https://portlookup.com/port-322/

Related ports

554/tcp (unencrypted RTSP, reportedly the more common default)

Primary use

default port for the rtsps:// URI scheme (RTSP over TLS), per RFC 7826

Other/unofficial uses

RTSP/RTSPS-capable IP cameras (e.g., Axis, Bosch), media servers/toolkits (FFmpeg, GStreamer, MediaMTX, Ant Media Server)

Security implications

RTSPS secures the control/authentication channel via TLS but not necessarily the media stream (needs SRTP for that); should stay restricted to trusted networks rather than public-facing

Typically seen on

IP camera and video-surveillance systems, streaming/media servers offering a secure RTSP control channel

Analyst note

most RTSP deployments reportedly still default to unencrypted 554 rather than RTSPS on 322; no hard adoption data found.

Port 322/udp is registered to IANA as rtsps (RTSPS), the same secure Real-Time Streaming Protocol control-channel service also registered on 322/tcp. In practice RTSPS runs over TLS, which requires a reliable stream transport, so the UDP registration looks like a paired-with-TCP registry convention rather than a real deployed service — traffic seen on 322/udp should be treated as anomalous and worth investigating rather than assumed to be a normal media session.

RTSPS pairs RTSP (port 554) session control with TLS encryption, and secondary sources associate it with IP cameras, network video recorders, and other streaming-media appliances that offer an encrypted control channel — chiefly surveillance and video-feed use cases. No first-party specification names a particular product, and no source describes an actual UDP-based RTSPS deployment; every documented implementation is TCP-only, since TLS assumes a reliable byte stream and a genuine UDP-encrypted session would need DTLS instead.

The IANA registry lists the assignee as Anders Klemets with no Registration Date, Modification Date, or RFC/reference recorded for either the TCP or UDP row, so those fields are reported here as blank rather than invented. General RTSP-family ports are noted by security writers as actively scanned for exposed, unauthenticated cameras and media servers; no scan-telemetry specific to 322/udp itself was found in this pass.

IANA assignment

rtsps — "RTSPS"; reference (blank — no RFC cited); assignee Anders Klemets; dual-registered 322/tcp + 322/udp (same service name/description/assignee/contact) [Confirmed] — IANA Service Name and Transport Protocol Port Number Registry

Range class

well-known (0–1023)

Prevalence

Unknown — no nmap-services or scan-telemetry figures found for 322/udp specifically in this pass [Unknown]

Related ports

322/tcp (same rtsps IANA registration); 554/tcp,udp (RTSP)

Primary use

RTSP session control/setup carried over TLS — an encrypted channel paired with plaintext RTSP on port 554

Other/unofficial uses

IP cameras, NVR/DVR systems, and streaming-media appliances offering an encrypted RTSP control channel (surveillance/CCTV)

Security implications

RTSPS control channels belong on trusted networks/VPNs, not public exposure; RTSP-family ports are generally scanned for exposed cameras; no 322/udp-specific incident or CVE identified

Typically seen on

no confirmed live deployments found (legacy/rare at most); if observed, investigate as misconfiguration, decoy, or paired-registration artifact

UDP-variant caveat

no confirmed real-world UDP-based RTSPS deployment found; TLS requires TCP, a genuine UDP variant would need DTLS instead — registration looks like a paired-with-TCP convention [Likely] — IANA registry

Analyst note

traffic on 322/udp is unusual — treat as anomalous/worth investigating rather than assume normal RTSPS media traffic, since every documented deployment is TCP-only.