Commonly used ports for various EDI communication protocols

Ports are typically used for secure and efficient data transmission between trading partners.

Here’s a list of commonly used ports for various EDI communication protocols. 

---

1. AS2 (Applicability Statement 2)

• Port:
  • 80 (HTTP)
  • 443 (HTTPS for secure communication)

---

2. FTP (File Transfer Protocol)

• Port:
  • 21 (Control channel for sending commands)
  • 20 (Data transfer channel, in active mode)

---

3. FTPS (FTP Secure)

• Port:
  • 21 (Explicit FTPS; uses FTP over TLS/SSL)
  • 990 (Implicit FTPS; secured connection starts automatically)

---

4. SFTP (SSH File Transfer Protocol)

• Port:
  • 22 (Encrypted connection using SSH)

---

5. OFTP (Odette File Transfer Protocol)

• Port:
  • 3305 (Default for OFTP over TCP/IP)
  • 6619 (Default for secure OFTP2 connections using TLS)

---

6. HTTP/HTTPS

• Port:
  • 80 (Standard HTTP)
  • 443 (Secure HTTPS)

---

7. PEPPOL (Pan-European Public Procurement Online)

• Port:
  • 80 (HTTP, less commonly used now)
  • 443 (HTTPS for secure data exchange)

---

8. SMTP (Simple Mail Transfer Protocol)

• Port:
  • 25 (Traditional SMTP; often blocked for outgoing traffic due to spam concerns)
  • 587 (SMTP with STARTTLS for encryption)
  • 465 (SMTPS for implicit SSL/TLS encryption)

---

9. VAN (Value-Added Network)

• Port:
  • Port numbers vary based on the VAN provider. Typically, VANs use secure connections like HTTPS (443) or AS2 (80/443).

---

10. MQ (Message Queuing)

• Port:
  • 1414 (IBM MQ default port)
  • 443 (For secure MQ connections using TLS/SSL)

---

11. MFT (Managed File Transfer)

• Port:
  • 21/990 (FTPS)
  • 22 (SFTP)
  • 443 (HTTPS-based MFT solutions)

---

12. X.400

• Port:
  • 102 (Default X.400 protocol port over TCP/IP)

---

13. REST APIs

• Port:
  • 443 (HTTPS for secure REST API calls)
  • 80 (HTTP, not recommended for sensitive data)

---

14. SOAP APIs

• Port:
  • Same as REST APIs, typically 443 (HTTPS) and 80 (HTTP).