360
Summary
- // typical exposure
- Anomalous (rarely legitimately open) — No confirmed legitimate service or protocol uses 360/tcp — IANA publishes only a bare service name with no RFC, spec, or description — so a responsive port 360/tcp has no documented benign explanation and should be treated as an anomaly worth investigating rather than assumed benign.
- // analyst note
- An open port 360/tcp has no confirmed legitimate explanation in current documentation — treat as anomalous and investigate as a possible misconfiguration, forgotten legacy service, or decoy/backdoor.
- // if you see it open
- No documented legitimate application or protocol uses 360/tcp, and no malware or trojan association is confirmed -- no named malware family, CVE, or dated incident ties a threat to this port. An unrelated product, Veriato's 'Recon/360' employee-monitoring software, does not use this port despite the name coincidence.
About port 360/tcp.
Port 360/tcp is registered with IANA under the service name scoi2odialog, but the registry gives no protocol description, no RFC reference, and no other public documentation exists describing what the service does — so there is no confirmed legitimate reason for this port to be reachable from the public internet, and it should be treated as unexplained rather than assumed safe.
The IANA Service Name and Transport Protocol Port Number Registry lists 360 as dual-assigned on TCP and UDP, both under scoi2odialog, with assignee/contact Keith Petley. The Reference, Registration Date, and Modification Date columns are all blank, consistent with an older assignment that predates IANA's more detailed registration paperwork.
No credible vendor documentation, blog post, or forum thread was found naming a specific application that generates traffic on TCP 360 today. Generic "common ports" reference sites mirror the bare IANA registration without adding real usage detail, and an unrelated employee-monitoring product, Veriato's "Recon/360," does not actually use this port despite the coincidental name.
No malware or trojan association is confirmed for this port either: no named malware family, CVE, or dated incident report ties any threat to TCP 360.
- IANA assignment
scoi2odialog— dual-registered 360/tcp + 360/udp; assignee/contact Keith Petley; Reference/Registration Date/Modification Date all blank [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry line 705-706; IANA registry- Range class
- well-known (0–1023) [Confirmed]
- Prevalence
- Unknown — no nmap-services frequency data or scanning telemetry surfaced in this pass [Unknown]
- Related ports
- other sparsely-documented legacy IANA registrations in the 300s block
Primary use
Unknown — no protocol specification, RFC, or public documentation found for scoi2odialog
Other/unofficial uses
none verified; generic port-list aggregator sites mirror the bare IANA registration without adding usage detail
Security implications
no confirmed legitimate use, and no confirmed malware/trojan association — no named malware family, CVE, or dated incident was found [Confirmed absence in sources checked]
Typically seen on
no known typical deployment; a responsive host is an anomaly [Unknown]
- Analyst note
- An open port 360/tcp has no confirmed legitimate explanation in current documentation — treat as anomalous and investigate as a possible misconfiguration, forgotten legacy service, or decoy/backdoor.
About port 360/udp.
Port 360/udp is registered with IANA under the name scoi2odialog, but no confirmed protocol specification, RFC, or documented legitimate use was found, and the port carries a historical, unconfirmed trojan/virus C2 flag, so an open 360/udp is Anomalous — unusual and worth investigating rather than an established, safe baseline.
The IANA Service Name and Transport Protocol Port Number Registry lists 360 as scoi2odialog on both TCP and UDP, assigned to Keith Petley. The Reference column is blank (no RFC is cited) and the Registration Date column is also blank, indicating the entry was registered without an accompanying published specification.
Because the registry entry gives only a name and no functional description, the underlying protocol is unclear. The name may hint at an SCO (Santa Cruz Operation) Unix-related dialog service, but this is speculation, not a confirmed source-backed fact, and no vendor documentation, blog post, or forum thread confirming current software using this port was found.
One third-party port-lookup database, AuditMyPC, flags both TCP and UDP port 360 as historically used by an unnamed trojan or virus for command-and-control communication. This is explicitly a past-use flag rather than a confirmation of an active, named threat, and no other source corroborates it.
- IANA assignment
scoi2odialog— description "scoi2odialog"; reference (blank); assignee Keith Petley; dual-registered 360/tcp + 360/udp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry- Range class
- well-known (0–1023) [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry
- Prevalence
- Unknown — no nmap-services or scan-telemetry data surfaced for this port [Unknown]
- Related ports
- 360/tcp (dual-registered scoi2odialog) [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry-706
Primary use
Unknown — no RFC or protocol spec found beyond the registered name; possibly an SCO Unix-related dialog service, unconfirmed
Other/unofficial uses
none confirmed [Unknown]
Security implications
AuditMyPC flags historical (unnamed, unconfirmed) trojan/virus C2 use on TCP/UDP 360; no other corroborating threat-intel source found
Typically seen on
Unknown — no confirmed deployment context [Unknown]
- Analyst note
- registration exists but is functionally undocumented; treat unexpected traffic on this port as worth investigating rather than assuming benign or malicious.
Service assignments.
| Name | Protocol | Description | Open frequency |
|---|---|---|---|
| scoi2odialog | UDP | — | 0.06% |
| scoi2odialog | TCP | — | 0.00% |
Service assignments from the IANA Service Name and Transport Protocol Port Number Registry, with open-frequency data from nmap-services.