393
Summary
- // typical exposure
- Internal-only — The port's registrant is an enterprise business-intelligence/ETL vendor (Meta5, Inc.) with no vendor documentation or public spec indicating a public-facing design, so any legitimate traffic is expected to stay within internal enterprise networks rather than face the public internet.
- // common applications
- Meta5 (Meta5, Inc. business-intelligence Traffic on this port is most often associated with the IANA registrant, Meta5, Inc., a business-intelligence/ETL vendor; this link is inferred from the registrant's identity rather than confirmed by vendor documentation naming port 393 explicitly, and no independently corroborated sightings of active use were found.
- // analyst note
- treat an unexpected open port 393 as low-prevalence rather than assume routine service; verify deployment context (Meta5 BI/ETL software) before dismissing as benign.
- // if you see it open
- No CVE or malware family is documented against TCP/393. A consumer port-lookup aggregator (auditmypc.com) marks the port 'Virus/Trojan: No'. Its 'Data Interpretation System (dis)' label matches the nmap-services corpus name 'dis', which covers BOTH 393/tcp and 393/udp (functions/_lib/port-data.json); 'Data Interpretation System' is only the udp line's comment, while the tcp line's comment reads 'meta5' — the IANA registration name 'meta5' is separate from the nmap-services name. No corroborated sightings of active use in the wild were found.
About port 393/tcp.
Port 393/tcp is registered with IANA as meta5, tied to the business-intelligence/ETL vendor Meta5, Inc.; no public specification documents its wire protocol, so it should not be treated as an internet-facing service — any legitimate use would be confined to internal enterprise networks rather than exposed to the public internet.
IANA's registry gives only a bare entry: service name meta5, description "Meta5," dual-registered on both 393/tcp and 393/udp, assignee/contact [Jim_Kanzler]. The Reference column is blank (no RFC), and neither a registration nor modification date is recorded.
The registrant, Jim Kanzler, is independently confirmed as founder and CEO of Meta5, Inc., a business-intelligence and data-integration ("ETL, query, reporting") software vendor founded in 2000, whose flagship product line traces back to IBM's Intelligent Decision Server. It is reasonable to infer the port was reserved for that company's client/server communication, but no vendor documentation was found stating that a current Meta5 product actually listens on port 393 — this specific linkage is inferred from registrant identity, not directly documented.
No corroborated, dated sightings of software actively using TCP/393 in the wild were found. A consumer port-lookup aggregator, auditmypc.com, labels the port "Data Interpretation System (dis)." That is not an aggregator error: the nmap-services corpus (this site's own tooling) names BOTH 393/tcp and 393/udp dis, with a comment field of "meta5" on the tcp line and "Data Interpretation System" on the udp line — see the udp companion entry. So dis is the nmap-services name for the whole port, distinct from the IANA registration name meta5 shared by both transports; what differs by transport is only the descriptive comment.
- IANA assignment
meta5— "Meta5"; reference (blank — no RFC cited); assignee/contact[Jim_Kanzler]; dual-registered 393/tcp + 393/udp [Confirmed] — IANA the IANA Service Name and Transport Protocol Port Number Registry- Range class
- well-known (0–1023) [Confirmed]
- Prevalence
- nmap-services open-frequency for 393/tcp ≈0.000000 [Confirmed] — nmap-services dataset (this site's own tooling); a recorded frequency of 0 reflects presence in the corpus with zero observed open instances, not an absence of data
- Related ports
- no documented cluster or grouping was identified for this service
Primary use
no RFC or public spec exists; IANA gives only the name/description. Registrant Jim Kanzler is confirmed founder/CEO of Meta5, Inc., a BI/ETL/data-integration vendor founded 2000 — inferred (not vendor-documented) link to that company's software
Other/unofficial uses
none independently corroborated; no forum or vendor sightings of active use were found [Unknown]
Security implications
no CVE or malware family documented against this port; one consumer aggregator (auditmypc.com) marks "Virus/Trojan: No" and separately lists the label "Data Interpretation System (dis)" — dis is the nmap-services corpus name for BOTH 393/tcp and 393/udp; "Data Interpretation System" is only the udp line's comment, while the tcp line's comment reads "meta5"
Typically seen on
presumed enterprise deployments of Meta5, Inc. BI/ETL software (inferred, not vendor-confirmed); otherwise essentially unseen [Unknown]
- Analyst note
- treat an unexpected open port 393 as low-prevalence rather than assume routine service; verify deployment context (Meta5 BI/ETL software) before dismissing as benign.
About port 393/udp.
Port 393/udp is registered with IANA as meta5, tied to the same business-intelligence/ETL vendor, Meta5, Inc., as its tcp companion; no public specification documents its wire protocol, so it should not be treated as an internet-facing service — any legitimate use would be confined to internal enterprise networks rather than exposed to the public internet.
IANA registers the service name meta5 — description "Meta5" — on both 393/tcp and 393/udp, assignee [Jim_Kanzler], with a blank Reference field (no RFC is cited for the assignment). Jim Kanzler is independently confirmed as founder/CEO of Meta5, Inc., a business-intelligence and data-integration ("ETL, query, reporting") vendor founded in 2000, whose product line traces to IBM's Intelligent Decision Server — see the tcp companion entry, sourced to meta5.us and theorg.com. No independent corroboration was found for a separate narrative (a distinct 1990s-era product later absorbed into a Cognos/IBM lineage), so it is not asserted here. Separately, the nmap-services corpus (this site's own tooling) names BOTH 393/tcp and 393/udp dis — distinct from the IANA registration name meta5 shared by both transports — with a comment field of "Data Interpretation System" on the udp line and "meta5" on the tcp line; the tcp line's comment reuses the IANA name as free text, but the nmap-services NAME itself is dis for both transports. No protocol specification beyond the bare registry entry was located.
No vendor documentation, blog posts, or forum/support threads were found tying any specific current software to port 393/udp; as with the tcp side, the link to Meta5, Inc.'s BI/ETL product is inferred from the registrant's identity rather than vendor-confirmed. Older port-database mirror sites list the port but attribute no application with sourced evidence, so those are not treated as corroboration.
No dates are published for the IANA registration itself, and none are fabricated here. Overall confidence is Medium: the IANA registration facts are confirmed against the registry, but the protocol's real-world usage and current relevance are effectively unknown.
- IANA assignment
meta5— "Meta5"; reference (blank — no RFC cited); assignee[Jim_Kanzler]; dual-registered 393/tcp + 393/udp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry (line 780)- Range class
- well-known (0–1023) [Confirmed] — port number 393
- Prevalence
- nmap-services open-frequency for 393/udp ≈0.001302 [Confirmed] — nmap-services dataset (this site's own tooling)
- Related ports
- no documented cluster or grouping was identified for this service
Primary use
no RFC or public spec exists; IANA gives only the name/description. Registrant Jim Kanzler is confirmed founder/CEO of Meta5, Inc., a BI/ETL/data-integration vendor founded 2000 — inferred (not vendor-documented) link to that company's software, shared with the tcp companion entry
Other/unofficial uses
nmap-services separately records 393/udp under the name dis / "Data Interpretation System"
Security implications
no CVEs, threat-intel, or scanning-report data specific to 393/udp found; the registrant is an enterprise BI/ETL vendor, so legitimate traffic is expected to stay within internal networks
Typically seen on
presumed enterprise deployments of Meta5, Inc. BI/ETL software (inferred, not vendor-confirmed); otherwise essentially unseen [Unknown]
- Analyst note
- treat an unexpected open port 393/udp as low-prevalence rather than assume routine service; verify deployment context (Meta5 BI/ETL software) before dismissing as benign.
Service assignments.
| Name | Protocol | Description | Open frequency |
|---|---|---|---|
| dis | UDP | Data Interpretation System | 0.13% |
| dis | TCP | meta5 | 0.00% |
Service assignments from the IANA Service Name and Transport Protocol Port Number Registry, with open-frequency data from nmap-services.