362

Port 362/tcp is a formally registered but essentially undocumented IANA assignment; no confirmed application uses it, and there is no basis for saying whether it belongs on the public internet or not. IANA lists the service name srssend with the description "SRS Send," but no RFC, no protocol specification, and no registration date accompany the entry.

The registrant of record is Curt Mayer, and the assignment is dual-registered for both TCP and UDP. Beyond that bare label, nothing further is publicly documented: no vendor spec, no client/server software, and no protocol behavior description have been located.

A name-string collision is worth flagging and rejecting: "SRS" here is unrelated to the well-known email anti-spam mechanism Sender Rewriting Scheme, which does not use a dedicated port at all. Treat any search hit conflating the two as a false friend, not evidence about this port's function.

No credible, dated security or exposure reporting is tied specifically to 362/tcp. One port-lookup aggregator (auditmypc.com) displays a generic "not currently flagged as infected" / trojan-history disclaimer, but that boilerplate is templated across the site's entire port catalog and is not a sourced finding about this port — it should not be read as a real security signal.

IANA assignment

srssend — "SRS Send"; reference (blank — no RFC cited); assignee/contact [Curt_Mayer]; dual-registered 362/tcp + 362/udp [Confirmed] — IANA Service Name and Transport Protocol Port Number Registry

Range class

well-known (0–1023)

Prevalence

no scan-frequency/telemetry data located for this port [Unknown]

Related ports

none specific identified [Unknown]

Primary use

Unknown beyond the bare IANA label; no protocol spec, RFC, or vendor documentation publicly available

Other/unofficial uses

none found [Unknown]

Security implications

no CVE, no confirmed malware association, no dated exposure/scanning reports specific to this port; a generic aggregator "trojan history" disclaimer is templated boilerplate, not a sourced finding

Typically seen on

not documented in available sources; no confirmed real-world deployments [Unknown]

Analyst note

the "SRS Send" name is unrelated to the email Sender Rewriting Scheme (SRS) anti-spam mechanism — a name-string false friend, not evidence of function [Confirmed] — cross-check performed during research

Port 362/udp is registered with IANA under the service name srssend ("SRS Send"), but no RFC, protocol specification, or vendor documentation describing what actually runs on it has been found, so whether legitimate traffic on this port belongs on the public internet cannot be confirmed. Given the absence of any established software or protocol tied to it, an analyst should treat a live 362/udp responder as unexplained rather than assume it is safe or expected.

IANA's Service Name and Transport Protocol Port Number Registry lists 362 as dual-registered on both TCP and UDP under the same name and description, with the assignee recorded as [Curt_Mayer] and a blank Reference field — meaning no RFC or specification was ever cited for the assignment. The Registration Date and Modification Date columns are also empty in the registry export, so the exact assignment date is unknown and is not fabricated here.

Web research beyond the bare registry entry turned up nothing further: no forum threads, vendor knowledge-base articles, or malware/IDS writeups mention specific software using UDP port 362, and generic port-lookup mirror sites only restate the IANA label without adding detail. This is consistent with 362/udp being a registered-but-effectively-undeployed name rather than an actively used service.

IANA assignment

srssend — "SRS Send"; reference (blank — no RFC cited); assignee [Curt_Mayer]; dual-registered 362/tcp + 362/udp [Confirmed] — IANA Service Name and Transport Protocol Port Number Registry

Range class

well-known (0–1023) [Confirmed] — port number falls in the well-known range

Prevalence

Unknown — no nmap-services or telemetry frequency data captured in this research pass [Unknown]

Related ports

362/tcp — the same srssend registration, dual-registered by IANA with an identical description ("SRS Send") and the same assignee/contact [Curt_Mayer]; a service-name and assignee search of the cached registry returns these two rows and no others, so 362/tcp is the only port related to this one by registration

[Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry srssend 362/tcp

Primary use

Unknown — no protocol specification or technical documentation found beyond the bare IANA label "SRS Send"

Other/unofficial uses

none found — no community-sourced sightings of specific software using 362/udp surfaced

Security implications

no CVEs, advisories, or exposure/scanning writeups found tied to 362/udp [Unknown]

Typically seen on

Unknown — no observed deployments found [Unknown]

Analyst note

A registered-but-undocumented port; an open/responsive 362/udp has no known legitimate explanation and should be investigated as unexplained.