whatportis.com
suggest an edit →

Port 351MATIP-Type B

MATIP-Type B (Mapping of Airline Traffic over Internet Protocol) facilitates the transmission of traditional airline reservation and operational traffic over IP networks. It allows legacy airline proprietary protocols to be encapsulated and sent across TCP/IP or UDP/IP, enabling seamless integration with modern communication infrastructure while maintaining support for existing airline applications..

inNetwork ServicesSystemCloud
transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
4/10

caution

lookups
8,716

rank 580 of 993 · top 58%

Technical Details

what runs on :351

The MATIP protocol, standardized by IETF as RFC 2351, enables airline applications relying on proprietary protocols like SITA X.25 to migrate onto IP-based networks efficiently. MATIP is designed to map various airline-specific message formats into TCP or UDP datagrams, offering support for applications such as reservations, messaging, and operational data. It acts as a lightweight encapsulation, maintaining data integrity and protocol framing inside the IP transport.

Port 351 is designated for MATIP-Type B sessions, typically used for server-side implementations receiving client connections. MATIP provides a minimalistic approach, simplifying the adaptation layer between legacy airline data streams and modern IP stacks without requiring complex gateways. It supports both connection-oriented (TCP) and connectionless (UDP) transport, granting flexibility based on performance or reliability needs.

Due to its functionally critical role within airline data infrastructure, MATIP promotes interoperability among carriers and service providers, reducing reliance on expensive legacy networking solutions. Its implementation allows airlines to continue using existing back-office systems over newer, cost-effective IP networks, improving scalability and maintaining compliance with aviation communication standards.

Security Information

exposure of :351

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 and authentication by design, making plaintext data susceptible to eavesdropping and man-in-the-middle (MITM) attacks
  • Susceptibility to IP-based attacks such as spoofing or session hijacking
  • Vulnerability to Denial of Service (DoS) attacks due to open UDP or persistent TCP connections

Common mitigations:

  • Employ IPsec or VPNs to provide encryption and secure tunnels for MATIP traffic
  • Implement network segmentation and firewall rules to restrict access strictly to trusted airline networks and partners
  • Use ingress and egress filtering alongside intrusion detection systems (IDS) to detect anomalies and prevent unauthorized connection attempts
  • Monitor MATIP network endpoints for unusual traffic flows or access attempts indicating attempted compromise

Related Ports

all 604 in network services →

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

portservicerisk
:9080Groove RPCcaution
:6543Jetnetcaution
:5938TeamViewercaution
:8291Winbox MikroTik Admincaution
:3233WhiskerControl Protocolcaution
:3268Microsoft Global Catalog (GC)caution
:135Microsoft EPMAPcaution
:3128Tatsoft Default HTTP Proxycaution

risk mix of the 8 listed

  • caution100%

0 of 8 encrypted