Network port detail · UDP/TCP

493

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

Summary

// typical exposure
Internal-only — This is a legacy vendor-registered assignment for Fujitsu's proprietary FNA host-networking stack with no documented public-internet role, so it should never be exposed beyond an internal/legacy environment if it runs at all.
// analyst note
An open 493/tcp is rare and has no documented modern legitimate driver outside legacy Fujitsu FNA contexts — treat an unexpected hit as worth investigating rather than routine.
// if you see it open
No CVE is recorded in the NVD and no malware family is documented against port 493 as of an August 2026 search. AuditMyPC's page carries its standard disclaimer sentence above a 'Virus/Trojan: No' verdict, which is a negative finding, not evidence of association. SANS ISC showed no populated scanning-activity data for this port at fetch time.
[ 01 ] — Context

About port 493/tcp.

Updated  ·  Confidence: Likely

Port 493/tcp carries ticf-2, IANA's "Transport Independent Convergence for FNA" assignment; it is a legacy vendor-registered port with no evidence of legitimate public-internet use, so it should stay internal-only if it is running at all.

IANA's Service Names and Port Numbers registry lists 493/tcp and 493/udp identically as ticf-2, assignee Mamoru Ito, with a blank Reference field — meaning no RFC or other standards-track document was ever attached to the assignment. FNA (Fujitsu Network Architecture) is Fujitsu's legacy proprietary mainframe/host networking stack, and "ticf" most plausibly denotes a transport-independent convergence function that bridges FNA traffic onto TCP/IP, though IANA's own text does not spell this out further.

No credible vendor documentation, blog post, or forum thread was found in an August 2026 search naming specific software that generates traffic on this port. Generic port-lookup aggregators (SpeedGuide, AuditMyPC, SANS ISC, adminsub.net) simply restate the IANA registry line rather than documenting an observed application, and SANS ISC's live port-493 activity page showed no populated scan data at fetch time.

No CVE or malware family is documented against port 493 as of an August 2026 search. AuditMyPC's port-493 page carries the site's standard disclaimer sentence directly above its own "Virus/Trojan: No" verdict — read correctly, that is a negative finding, not evidence of any association.

IANA assignment
ticf-2 — "Transport Independent Convergence for FNA"; reference (blank — no RFC cited); assignee Mamoru Ito; dual-registered 493/tcp + 493/udp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry ticf-2 493/tcp
Range class
system/well-known (0–1023) [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry ticf-2 493/tcp
Prevalence
nmap-services open-frequency 493/tcp = 0.000025 (~0.0025%); 493/udp = 0.00056 (~0.056%) [Confirmed] — this site's own tooling
Related ports
other system-range Fujitsu/legacy host-integration assignments in the low 400s–500s block; contrast the /port/ hub

Primary use

vendor-registered transport-convergence function for Fujitsu's FNA (Fujitsu Network Architecture) mainframe/host networking; no RFC attached

[Likely] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?page=9

Other/unofficial uses

none documented

[Unknown] — no source located as of an August 2026 search

Security implications

no CVE or malware association documented as of August 2026; AuditMyPC boilerplate correctly read as a negative, not a finding; no notable scanning activity observed on SANS ISC

[Likely] — https://isc.sans.edu/data/port/493, https://www.auditmypc.com/tcp-port-493.asp

Typically seen on

legacy Fujitsu FNA-integrated host/mainframe environments, if anywhere; otherwise an anomaly

[Unknown] — no direct sighting located
Analyst note
An open 493/tcp is rare and has no documented modern legitimate driver outside legacy Fujitsu FNA contexts — treat an unexpected hit as worth investigating rather than routine.
[ 02 ] — Context

About port 493/udp.

Updated  ·  Confidence: Moderate

Port 493/udp carries ticf-2, IANA's registered name for "Transport Independent Convergence for FNA"; it is a legacy, no-RFC registration with no evidence of active modern deployment, so it should never appear as internet-facing traffic and a response on it is a signal worth investigating rather than a normal service.

IANA registered 493/udp (and the paired 493/tcp) to ticf-2 under assignee Mamoru Ito, with a blank Reference column — no citing RFC exists in the registry. "FNA" most plausibly points to Fujitsu Network Architecture, a mainframe/host networking architecture, and ticf-2 pairs with a companion service ticf-1 on port 492, consistent with a narrow vendor-specific transport-convergence pairing rather than a broadly deployed general-purpose protocol.

No authoritative technical specification beyond the bare IANA entry was found, and no vendor documentation, forum sighting, or malware report ties concrete software to this port as of an August 2026 search. nmap-services records an open-frequency of 0.00056 for 493/udp (0.000025 for 493/tcp), both near the low end of the measured range, consistent with a port that is essentially never seen open in practice.

IANA assignment
ticf-2 — "Transport Independent Convergence for FNA"; reference (blank — no RFC cited); assignee Mamoru Ito; dual-registered 493/tcp + 493/udp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry ticf-2 493/udp
Range class
well-known/system (0–1023) [Confirmed] — this site's own tooling
Prevalence
nmap-services open-frequency 493/udp ≈ 0.00056 (~0.056%); 493/tcp ≈ 0.000025 [Confirmed] — this site's own tooling
Related ports
492/tcp+udp (ticf-1, companion registration) [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry ticf-1 492/udp

Primary use

Legacy vendor-oriented transport-convergence service; no RFC, no evidence of broad deployment

[Likely] — IANA registry (no RFC cited)

Other/unofficial uses

Possibly linked to Fujitsu Network Architecture (FNA) naming convention; pairs with ticf-1 on port 492

[Likely] — inferred from the naming pattern, no single authoritative document located

Security implications

essentially never legitimately open; no CVE or malware association found as of an August 2026 search

[Likely] — https://isc.sans.edu/data/port/493

Typically seen on

not observed in normal deployments; an open instance is an anomaly [Unknown]

Analyst note
An open 493/udp is statistically rare and has no established legitimate modern use — treat as anomalous and investigate rather than assume normal service traffic.
// registry data

Service assignments.

2 entries
// IANA / nmap services registry
NameProtocolDescriptionOpen frequency
ticf-2 UDP Transport Independent Convergence for FNA 0.06%
ticf-2 TCP Transport Independent Convergence for FNA 0.00%
IANA name
ticf-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.