244
Summary
- // if you see it open
- No CVEs, malware families, or active-scanning campaigns documented against port 244 in available sources; one secondary source (auditmypc.com) explicitly lists no known virus/trojan association. A responsive listener today would be unusual for either protocol.
- // analyst note
- a listener on 244/tcp or 244/udp is unusual today; treat as either an artifact of very old SOHO hardware or as worth independent investigation rather than assuming a known modern service.
About port 244/tcp.
Port 244 is registered with IANA as inbusiness for both TCP and UDP, assigned to Derrick Hisatake, with the description field simply reading "inbusiness" and both the Reference (RFC) and Registration/Modification Date columns blank in the authoritative registry — a distinctly bare registration compared to ports with formal RFC backing. Community port-database sites (not IANA, not vendor documentation) tie this historical assignment to Dayna Communications' "InBusiness" line of small-office/home-office (SOHO) networking hardware from the mid-to-late 1990s — items such as low-cost hubs, routers, and print servers marketed to small networks. Dayna Communications was acquired by Intel in 1998, and the InBusiness product line is reported to have been discontinued around 2002, after which any protocol distinct to this port would have faded from active use. No CVEs, malware families, or active-scanning campaigns are documented against port 244 in available sources, and no currently maintained software is known to use it. For an analyst, a listener on 244/tcp or 244/udp today is unusual and worth investigating case-by-case rather than assuming it maps to any well-known modern service — legitimate traffic on this port would be a rare artifact of decommissioned Dayna hardware, if it appears at all.
- IANA assignment
inbusiness; reference (blank — no RFC cited in the registry); assignee/contact[Derrick_Hisatake]; dual-registered 244/tcp + 244/udp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry-558; https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv- Registration/Modification dates
- blank in the IANA registry (reported blank, not inferred) [Confirmed] — same source
- Range class
- well-known (0–1023) [Confirmed]
- Prevalence
- no nmap-services open-frequency figure found in this pass [Unknown]
- Related ports
- no directly related port cluster identified for this legacy vendor-specific assignment [Unknown]
Primary use (historical)
reported association with Dayna Communications' "InBusiness" SOHO networking hardware line, circa 1997; Dayna acquired by Intel in 1998; product line reportedly discontinued ~2002
Typically seen on
legacy/decommissioned Dayna InBusiness SOHO equipment, if anywhere; otherwise anomalous
- Modern software usage
- none identified in this research pass [Unknown]
- Security/malware association
- no CVEs or malware family attributed to port 244 found in available sources; one secondary source explicitly logs no known trojan/virus association [Unknown] — https://www.auditmypc.com/tcp-port-244.asp
- Analyst note
- a listener on 244/tcp or 244/udp is unusual today; treat as either an artifact of very old SOHO hardware or as worth independent investigation rather than assuming a known modern service.
About port 244/udp.
Port 244/udp is registered with IANA under the service name inbusiness, described simply as "inbusiness," with assignee and contact both listed as [Derrick_Hisatake] and no reference (RFC) column populated. The assignment is dual-registered: the adjacent row for 244/tcp carries the identical service name, assignee, and contact, with every other column equally blank, so this is a single paired reservation rather than two independently-justified entries. No registration date, modification date, or IANA reference is published for either half of the pair in the cached registry export, and none of those values is invented here. Corroborating web research ties the "inbusiness" name to Dayna Communications' InBusiness line of small-office network hubs and switches from the late 1990s, a product family that Intel continued under its own brand after acquiring Dayna Communications in 1998 (confirmed by a contemporaneous Intel press release). Secondary port-reference sites describe the InBusiness hub line as discontinued by roughly 2002, after which no further software is documented as using this port; that discontinuation date, however, comes only from secondary sources and is not IANA-confirmed. No trojan, backdoor, or malware association appears in the standard bad-ports references checked for this port, and no current legitimate production use is expected given the product line's age. For an analyst, an unexpected response on 244/udp today is more plausibly a coincidental listener, a misconfigured legacy device, or noise than an active InBusiness hub, since the hardware it names has been off the market for over two decades.
- IANA assignment
inbusiness— description "inbusiness"; assignee and contact[Derrick_Hisatake]; reference column blank; dual-registered with 244/tcp (identical service name/assignee/contact) [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry line 558 (tcp counterpart: line 557); cross-checked against https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt- Range class
- well-known (0–1023) [Confirmed]
- Registration/modification dates
- blank in the cached IANA CSV export and not published for this legacy entry in the live registry text file either — recorded as Unknown, not fabricated [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry line 558; https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt
- IANA reference (RFC)
- none listed — left blank per policy, not invented [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry line 558
- Prevalence
- nmap-services observed open-frequency 244/udp ≈ 0.000461 (very low — roughly 5 in 10,000 scanned hosts in the nmap-services sample) [Confirmed] — nmap-services dataset; the dual-registered 244/tcp row records 0.000000 in the same dataset [Confirmed] — nmap-services dataset. The figure is consistent with the associated product's discontinuation: current legitimate use is expected to be negligible [Likely]
- Related ports
- 244/tcp (the paired dual registration with identical assignee/service name)
Primary use
name reservation historically tied to Dayna Communications' "InBusiness" line of small-office network hubs/switches (management function), continued as "Intel InBusiness" after Intel's 1998 acquisition of Dayna Communications [Likely] — https://www.intel.com/pressroom/archive/releases/1998/IB071398.HTM, https://www.auditmypc.com/tcp-port-244.asp, https://tcp-udp-ports.com/port-244.htm
Other/unofficial uses
none documented beyond the InBusiness hub/switch product line; secondary sources describe the line as discontinued around 2002, after which no other software is known to use this port (discontinuation year is a secondary-source claim, not IANA-confirmed)
Security implications
no trojan/malware/backdoor association found in standard bad-ports references checked (Trend Micro-style and Gary Kessler lists were not directly consulted this pass; auditmypc.com marks this port "Virus/Trojan: No" with only generic boilerplate, no incident specific to 244) — a sourced null result rather than a confirmed clean bill of health
Typically seen on
legacy Dayna/Intel InBusiness hub or switch management interfaces, if present at all; otherwise unexpected on modern networks
- Analyst note
- a response on 244/udp is unusual given the age and discontinuation of the associated hardware; treat as a legacy artifact, coincidental listener, or worth investigating rather than an actively-maintained service.
Service assignments.
| Name | Protocol | Description | Open frequency |
|---|---|---|---|
| dayna | UDP | — | 0.05% |
| dayna | TCP | inbusiness | 0.00% |
Service assignments from the IANA Service Name and Transport Protocol Port Number Registry, with open-frequency data from nmap-services.