Port 350MATIP Type A

MATIP Type A enables the transportation of traditional airline reservation, ticketing, and messaging data over IP networks, replacing legacy airline communication systems and streamlining operations across global aviation networks..

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
4/10

caution

lookups
9,346

rank 513 of 993 · top 52%

Technical Details

what runs on :350

Overview

MATIP (Mapping of Airline Traffic over Internet Protocol) defines standardized methods for transporting traditional airline messaging protocols like SITA Type A on IP-based networks. Port 350 specifically corresponds to MATIP Type A, used worldwide in the airline industry to carry vital operational communication data.

Protocol Details

This protocol encapsulates airline legacy messaging formats, such as reservation data, baggage handling, and flight operations, within TCP or UDP packets. MATIP facilitates seamless migration of airlines’ proprietary mainframe or X.25 message-switching systems to modern IP infrastructure, improving cost-effectiveness and interoperability without modifying existing application software.

Implementation

MATIP Type A usually operates via dedicated airline network providers partnered with IATA, ensuring end-to-end delivery through predefined gateways. It enables multiple virtual circuits over a single physical IP link, adhering to IATA standards, ensuring compatibility, and often coexisting alongside other airline protocols.

Security Information

exposure of :350

risk score

4/ 10caution

worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.

network services averages 3.9 across 604 ports — this one sits 0.1 above.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

Common Vulnerabilities

  • Lack of encryption: As MATIP itself doesn’t mandate encryption, data—including sensitive passenger or operational information—may be transmitted in cleartext, exposing it to interception.
  • Protocol spoofing: Attackers can attempt to inject fraudulent airline messages potentially affecting operations if authentication lacks.
  • Denial of Service (DoS): Because MATIP uses TCP and UDP, it can be vulnerable to floods or malformed packet attacks, disrupting communication.
  • Weak segmentation: Poorly segregated airline IP networks can widen exposure if compromised through MATIP services.

Mitigations

  • Encryption: Use IPsec or TLS-based tunnels to secure MATIP traffic over public or shared networks.
  • Network segmentation: Isolate MATIP servers on dedicated VLANs/subnets with strict firewall policies.
  • Access control: Deploy strong authentication for endpoints handling MATIP messages, including network-based ACLs.
  • Monitoring: Implement intrusion detection targeting anomalous MATIP traffic, and log communications for audit trails.
  • Patch management: Keep underlying systems and MATIP gateway software updated to mitigate vulnerabilities.

the 8 most looked-up other ports in network services — 604 ports carry that label.

risk mix of the 8 listed

  • caution100%

0 of 8 encrypted