184

Port 184/tcp is registered with IANA under the service name ocserver, description "OCServer," with assignee and contact both listed as Jerrilynn Okamura. The registration is dual — 184/udp carries the identical service name, description, and assignee/contact — but the registry's Registration Date, Modification Date, Reference, Service Code, Unauthorized Use Reported, and Assignment Notes columns are all blank for both rows, both in the locally cached registry CSV and confirmed against a live fetch of the IANA registry page. No RFC or other protocol specification is cited for this assignment, and no publicly documented software, vendor, or protocol behavior tied to the name "OCServer" could be located: third-party port-lookup aggregators (SpeedGuide, tcp-udp-ports.com, auditmypc.com, t1shopper.com, GRC's Port Authority, my-addr.com) simply mirror the bare IANA name and description without adding independent detail on an actual client/server implementation. This pattern — a well-known-range assignment (0–1023) with a named assignee but no reference, no spec, and no traceable software — is typical of an old/legacy IANA registration that was reserved but never developed into a documented, widely deployed protocol. On the security side, auditmypc.com's port-security aggregator explicitly reports no known virus or Trojan association for port 184 as of the check date, and no CVEs or active-scanning campaigns specific to 184/tcp were found. Because there is no known legitimate service behind this name, an analyst encountering an open 184/tcp should treat it as unusual and worth investigating rather than assuming any specific application, since "OCServer" itself is essentially undocumented outside the bare registry entry.

IANA assignment

ocserver — "OCServer"; assignee/contact Jerrilynn_Okamura; reference blank; dual-registered 184/tcp + 184/udp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry-455; https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=184

Range class

well-known (0–1023) [Confirmed]

Registration/modification dates

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

IANA reference/RFC

none listed in the registry entry; left blank per no-fabrication rule [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=184

Related ports

no directly related cluster identified; treat alongside other sparsely-documented legacy well-known-range assignments

Primary use / protocol behind "OCServer"

no protocol specification, vendor documentation, or actively-used software identified beyond the bare registry name; treated as Unknown rather than guessed

Security implications

auditmypc.com reports no known virus/Trojan association for this port (checked 2026-07-11); no CVEs or documented scanning campaigns specific to 184/tcp found in this pass

Typically seen on

no known legitimate deployment; an open 184/tcp is anomalous and worth investigating given the lack of a documented service behind the registration [Unknown]

Third-party mirrors

SpeedGuide, auditmypc.com, t1shopper.com, GRC Port Authority, my-addr.com all reproduce only the bare IANA name/description with no additional software detail [Likely] — https://www.speedguide.net/port.php?port=184; https://www.auditmypc.com/tcp-port-184.asp; http://www.t1shopper.com/tools/port-number/184/; https://www.grc.com/port_184.htm; http://ports.my-addr.com/tcp_port-udp_port-application-and-description.php?port=184

Port 184/udp is registered with IANA under the service name ocserver, described simply as "OCServer," with assignee and contact both listed as Jerrilynn Okamura. The registry entry is dual-registered — the identical service name, description, and assignee appear on 184/tcp as well — but the IANA Reference field is blank for both transports, so no RFC or other normative specification is cited for this assignment. Beyond the bare registry line, no independently documented software product, open-source project, or protocol specification tied to the name "ocserver" could be verified in this pass; what "OCServer" refers to in practice remains unknown rather than guessed. The only third-party commentary found, from AuditMyPC's port-lookup page, offers a generic "no known virus or trojan" disclaimer that is templated boilerplate repeated across many of that site's port pages rather than research specific to port 184, so it is treated as low-value color rather than substantive threat intelligence. No CVEs, malware families, or notable scanning campaigns were found associated with this port. Given the sparse public footprint, port 184/udp should be treated as an obscure, low-profile IANA registration: the nmap-services dataset puts its observed open-frequency at roughly 0.000461 (against 0.000013 on 184/tcp), while the software actually listening on it and any security significance remain Unknown as of 2026-07-11, and nothing here should be filled in with invented dates, RFCs, or attributions.

IANA assignment

ocserver — "OCServer"; reference (blank — no RFC cited in IANA registry); assignee/contact Jerrilynn Okamura; dual-registered 184/tcp + 184/udp [Confirmed] — IANA Service Name and Transport Protocol Port Number Registry (cached CSV, row 455 udp / row 454 tcp); cross-confirmed live via IANA search page

Range class

well-known (0–1023) [Confirmed]

Prevalence

nmap-services observed open-frequency 184/udp ≈ 0.000461 (very low — roughly 5 in 10,000 scanned hosts in the nmap-services sample) [Confirmed] — nmap-services dataset; the dual-registered 184/tcp side is rarer still at ≈ 0.000013 [Confirmed] — nmap-services dataset

Related ports

184/tcp (identical registry entry; dual tcp/udp registration) [Confirmed] — IANA registry

Primary use

Unknown — no independently documented software, project, or protocol beyond the bare IANA registration name "ocserver" could be verified in this pass [Unknown]

Other/unofficial uses

Unknown — no third-party documentation found [Unknown]

Security implications

AuditMyPC lists a generic "Virus/Trojan: No" disclaimer for UDP 184, but this text is templated boilerplate repeated across many of the site's port pages rather than port-specific research; no CVEs or scanning-campaign associations found

Typically seen on

Unknown

Analyst note

Obscure, low-profile registration with almost no independent documentation; treat unexpected traffic on this port as an anomaly pending further identification rather than assuming a known-benign or known-malicious role.