492
Summary
- // typical exposure
- Anomalous (rarely legitimately open) — The service has no documented legitimate deployment, no cited spec, and is essentially never observed open in mass-scan data, so an open 492/tcp should be treated as an investigation-worthy anomaly rather than expected infrastructure.
- // analyst note
- An open 492/tcp has no documented legitimate use and is essentially unseen in mass-scan data; treat unexpected traffic as anomalous and worth investigating rather than assuming a known application.
- // if you see it open
- No CVE referencing port 492 is recorded in the NVD as of an August 2026 search. No credible source ties 492/tcp to a specific trojan or malware family as of the same search. The port is essentially never observed open in mass-scan telemetry, so unexpected traffic on it is anomalous and merits investigation.
About port 492/tcp.
Port 492/tcp carries ticf-1, IANA's registered "Transport Independent Convergence for FNA" service; no documentation of real-world deployment was found, so the port should stay internal-only (or simply closed) rather than face the public internet.
IANA's Service Name and Transport Protocol Port Number Registry lists ticf-1 on both 492/tcp and 492/udp with an identical description and blank Assignee and Reference columns — no RFC or vendor spec is cited. A companion entry, ticf-2, sits on port 493/tcp+udp, suggesting the two were registered as a pair for the same protocol family.
IANA does not expand what "FNA" stands for or give any protocol detail; no protocol specification, vendor document, or operational description of the service was located. What the convergence protocol actually does, and whether any shipping software implements it, is Unknown.
No community sightings of applications or services running on this port turned up in vendor docs, blogs, or forum threads. Scan/telemetry sources specific to port 492 were likewise not found. The nmap-services open-frequency for 492/tcp is 0.00005 (about 0.005% of scanned hosts), confirming the port is sampled but essentially never seen open.
- IANA assignment
ticf-1— "Transport Independent Convergence for FNA"; Reference column blank; Assignee column blank; dual-registered 492/tcp + 492/udp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry ticf-1 492/tcp- Range class
- system/well-known (0–1023) [Confirmed]
- Prevalence
- nmap-services open-frequency 492/tcp = 0.00005 (~0.005%); 492/udp = 0.00061 (~0.061%) [Confirmed] — this site's own tooling
- Related ports
- 493/tcp+udp (
ticf-2, registered as a companion service in the same convergence family)
Primary use
IANA-documented as "Transport Independent Convergence for FNA"; a companion entry ticf-2 is registered on 493/tcp+udp, implying a paired protocol family; IANA does not expand what "FNA" stands for or give any protocol detail, and no spec or vendor document describing operational behavior was found
Other/unofficial uses
none found; no community-sourced sightings of any application using this port [Unknown]
Security implications
no CVE recorded in NVD as of an August 2026 search; no confirmed malware/trojan association found in the same search
Typically seen on
Unknown — no observed hosts or deployment reports found
- Analyst note
- An open 492/tcp has no documented legitimate use and is essentially unseen in mass-scan data; treat unexpected traffic as anomalous and worth investigating rather than assuming a known application.
About port 492/udp.
Port 492/udp is registered with IANA under the short name ticf-1, described only as "Transport Independent Convergence for FNA"; no public specification, vendor documentation, or scanning report describes what actually generates traffic on it, so it should be treated as an obscure legacy assignment rather than a service that belongs on the public internet.
The IANA registration itself is solid: ticf-1 is dual-registered on both 492/tcp and 492/udp, with a blank Assignee field and a blank Reference field — there is no RFC or formal specification backing the entry, only the short name and description.
Beyond that registry line, the trail goes cold. A search across IANA, port-lookup aggregators (GRC Port Authority, WintelGuy), and general web sources as of August 2026 turned up no vendor documentation, blog post, or forum thread naming a real application that uses 492/udp, and IANA does not expand what "FNA" stands for or give any protocol detail.
Corpus telemetry backs up the obscurity: the nmap-services-derived open-frequency for 492/udp is 0.00061 (about 0.061%), recorded in this repo's this site's own tooling artifact, versus 0.00005 for the companion 492/tcp entry — both consistent with a rarely-if-ever-open legacy assignment rather than an actively deployed service.
- IANA assignment
ticf-1— "Transport Independent Convergence for FNA"; reference (blank — no RFC cited); assignee (blank); dual-registered 492/tcp + 492/udp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry ticf-1 492/udp- Range class
- well-known/system (0–1023) [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry ticf-1 492/udp
- Prevalence
- 492/udp open-frequency 0.00061 (~0.061%); 492/tcp 0.00005 [Confirmed] — this site's own tooling
- Related ports
- 492/tcp (same
ticf-1name, dual registration) [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry ticf-1 492/tcp
Primary use
registered name and description suggest FNA-related convergence signaling, but IANA gives no protocol detail, RFC, or spec beyond the short name
Other/unofficial uses
Unknown — no community-sourced sightings of an application using this port surfaced (GRC, WintelGuy, SpeedGuide all just restate the bare IANA name/description)
Security implications
no CVE or malware/trojan association found in sources checked as of an August 2026 search; near-zero open-frequency
Typically seen on
Unknown — no observed deployments found [Unknown]
- Analyst note
- Treat an open 492/udp as worth investigating rather than assuming legitimate use — the registry entry has no backing RFC, no known assignee, and no documented real-world deployment.
Service assignments.
| Name | Protocol | Description | Open frequency |
|---|---|---|---|
| ticf-1 | UDP | Transport Independent Convergence for FNA | 0.06% |
| ticf-1 | TCP | Transport Independent Convergence for FNA | 0.01% |
Service assignments from the IANA Service Name and Transport Protocol Port Number Registry, with open-frequency data from nmap-services.