Network port detail · UDP/TCP

374

Legent-2
Protocol(s)
UDP/TCP
Range
System (0-1023)

Summary

// typical exposure
Anomalous (rarely legitimately open) — No documented protocol, no confirmed active software, and registration to a defunct 1990s vendor mean 374/tcp has no expected legitimate purpose on a modern network and should be treated as anomalous if seen open.
// analyst note
A responsive port 374/tcp has no established legitimate modern use — investigate rather than assume it is expected traffic.
// if you see it open
No documented protocol or confirmed active deployment exists for 374/tcp; it is registered to a defunct 1990s mainframe-software vendor (Legent Corporation, acquired by CA in 1995) with no publicly known current use, no CVE, and no malware association found in this pass. An open 374/tcp should be treated as anomalous and worth investigating rather than expected legitimate traffic.
[ 01 ] — Context

About port 374/tcp.

Updated  ·  Confidence: Low

Port 374/tcp is registered to Legent Corporation under the IANA service name legent-2, but no RFC or public specification documents what protocol it actually carries; with no confirmed current deployment, a live listener on this port has no established legitimate use and should be treated as worth investigating rather than assumed benign.

IANA's Service Name and Transport Protocol Port Number Registry lists 374 as dual-registered on both TCP and UDP, with the service name legent-2, description "Legent Corporation," and assignee Keith Boyce. The Reference field is blank — IANA records no RFC or protocol document for this assignment, and that blank is preserved here rather than invented.

Legent Corporation was a mainframe and systems-management software vendor that was acquired by Computer Associates (CA) in 1995. The IANA record only ties the port to the company name; it does not describe a protocol, and no publicly documented specification for legent-2 traffic was located during this research pass.

Community-sourced sighting data (forum posts, blog write-ups, scan telemetry) could not be gathered this pass — the session's WebSearch budget was exhausted (200/200 used) before any query on this port could return results, and two secondary port-lookup sites (SpeedGuide, ports_db) returned HTTP 403 when fetched directly. No malware, backdoor, or CVE association was found or ruled out; the field is genuinely unresearched rather than confirmed clean.

IANA assignment
legent-2 — "Legent Corporation"; reference (blank — no RFC cited in IANA registry) [Confirmed] — IANA Service Name and Transport Protocol Port Number Registry
Range class
well-known (0–1023) [Confirmed] — port number falls below 1024
Prevalence
Unknown — no scanning/telemetry data (nmap-services frequency, Shodan/Censys) obtained this research pass [Unknown]
Related ports
none confirmed in the immediate 370s IANA block during this pass [Unknown]

Primary use

Unknown / not publicly documented; no RFC or protocol spec exists for legent-2

[Unknown] — IANA registry (blank Reference field)

Other/unofficial uses

none documented; Legent Corporation was a mainframe/systems-management software vendor acquired by Computer Associates (CA) in 1995

[Likely] — general Legent/CA corporate history, not port-specific documentation

Security implications

no documented protocol, no confirmed active deployment, no CVE or malware association found; an open 374/tcp should be treated as anomalous

[Unknown] — absence of findings across IANA, WebFetch, and (budget-limited) WebSearch passes

Typically seen on

not documented; presumed legacy/rare if seen at all [Unknown]

Assignee
Keith Boyce (Legent Corporation), dual-registered 374/tcp + 374/udp [Confirmed] — IANA registry
Analyst note
A responsive port 374/tcp has no established legitimate modern use — investigate rather than assume it is expected traffic.
[ 02 ] — Context

About port 374/udp.

Updated  ·  Confidence: Low

Port 374/udp is registered with IANA under the service name legent-2, described in the registry as "Legent Corporation" with assignee/contact Keith Boyce, but no protocol specification survives — so what actually runs on this port, and whether it belongs on the public internet, is unknown rather than confirmed either way.

The IANA Service Name and Transport Protocol Port Number Registry lists 374 as dual-registered on both TCP and UDP for legent-2, with description "Legent Corporation" and assignee/contact Keith Boyce, and no RFC or reference document cited. Only the Reference, Registration Date, and Modification Date fields are blank in the authoritative source — a blank column records the absence of a registered value, not a positive confirmation that no such document or date ever existed.

Legent Corporation was a mainframe and enterprise systems-management software vendor; it was acquired by Computer Associates (CA) in 1995, and the port-374 registration predates that acquisition. No vendor documentation, protocol write-up, or community sighting describing an actual service on 374/udp was located during this research pass — attempts to check secondary port databases (SpeedGuide, AdminSub) failed with HTTP errors, and no scan or exposure telemetry for the port was found either.

Given the near-total absence of protocol documentation, an analyst who sees 374/udp traffic should treat it as an unidentified legacy or vendor-specific registration rather than assume either a benign or malicious purpose — verification against the actual host and payload is the only reliable path.

IANA assignment
legent-2 — description "Legent Corporation"; reference blank; assignee and contact Keith Boyce; dual-registered 374/tcp + 374/udp [Confirmed] — IANA Service Name and Transport Protocol Port Number Registry
Range class
well-known (0–1023) [Confirmed]
Prevalence
Unknown — no nmap-services open-frequency or scan-telemetry data for 374/udp was found in this pass [Unknown]
Related ports
374/tcp (dual-registered, identical IANA entry) [Confirmed] — IANA registry

Primary use

Unknown — no protocol specification, RFC, or vendor documentation describing the service was found

[Unknown] — IANA registry

Other/unofficial uses

None found — no community-sourced sightings (vendor docs, blogs, forums) turned up software using UDP port 374 [Unknown]

Security implications

No CVE, malware association, or exposure/scanning data found for 374/udp; treat unexpected traffic as unidentified

[Unknown] — no source located

Typically seen on

Unknown — no deployment evidence found; would historically only be relevant to legacy Legent Corporation / CA systems-management environments if ever implemented [Unknown]

Vendor context
Legent Corporation, a mainframe/enterprise systems-management software vendor, was acquired by Computer Associates (CA) in 1995; registration predates the acquisition [Likely] — general vendor history, not independently re-cited this pass
Research limitations
SpeedGuide.net and AdminSub.net lookups failed (HTTP 403 / 522); only the IANA registry was successfully verified [Confirmed] — IANA registry
// registry data

Service assignments.

2 entries
// IANA / nmap services registry
NameProtocolDescriptionOpen frequency
legent-2 UDP Legent Corporation (now Computer Associates Intl.) 0.06%
legent-2 TCP Legent Corporation (now Computer Associates Intl.) 0.00%
IANA name
legent-2
Transport
TCP
Range
System (0-1023)

Service assignments from the IANA Service Name and Transport Protocol Port Number Registry, with open-frequency data from nmap-services.