Service Name and Transport Protocol Port Number Registry

Last Updated

  • 2026-10-22

Expert(s)

  • TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, and Michael Scharf
  • SCTP: Michael Tuexen
  • DCCP: Eddie Kohler and Yoshifumi Nishida

Reference

  • RFC 6335: Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry

Note

Service names and port numbers are used to distinguish between different services that run over transport protocols such as TCP, UDP, DCCP, and SCTP.

Service names are assigned on a First Come First Served basis, as described in RFC 6335.

Port numbers are divided into three ranges, with their uses and assignment procedures specified in Section 8.1.2 of RFC 6335:

The registration procedures for service names and port numbers are specified in RFC 6335, while the registration policies referenced above are defined in RFC 8126.

Assigned ports both System and User ports SHOULD NOT be used without or prior to IANA registration.

Assignment of a port number does not in any way imply an endorsement of an application or product, and the fact that network traffic is flowing to or from a registered port does not mean that it is "good" traffic, nor that it necessarily corresponds to the assigned service. Firewall and system administrators should choose how to configure their systems based on their knowledge of the traffic in question, not whether there is a port number registered or not.

Registration Forms

Available Formats

Service Name Port Number Transport Protocol Description Assignee Contact Registration Date Modification Date Reference Service Code Unauthorized Use Reported Assignment Notes
ethernet-ip-s 2221 tcp EtherNet/IP over TLS ODVA, Inc. Brian Batke 2015-05-28
ethernet-ip-s 2221 udp EtherNet/IP over DTLS ODVA, Inc. Brian Batke 2015-05-28
EtherNet-IP-1 2222 tcp EtherNet/IP I/O

IANA assigned this well-formed service name as a replacement for "EtherNet/IP-1".
Brian Batke Brian Batke New contact added for port 2222 on 2008-02-01
EtherNet/IP-1 2222 tcp EtherNet/IP I/O Brian Batke Brian Batke New contact added for port 2222 on 2008-02-01 This entry is an alias to "EtherNet-IP-1". This entry is now historic, not usable for use with many common service discovery mechanisms.
EtherNet-IP-1 2222 udp EtherNet/IP I/O

IANA assigned this well-formed service name as a replacement for "EtherNet/IP-1".
Brian Batke Brian Batke New contact added for port 2222 on 2008-02-01
EtherNet/IP-1 2222 udp EtherNet/IP I/O Brian Batke Brian Batke New contact added for port 2222 on 2008-02-01 This entry is an alias to "EtherNet-IP-1". This entry is now historic, not usable for use with many common service discovery mechanisms.
EtherNet-IP-2 44818 tcp EtherNet/IP messaging

IANA assigned this well-formed service name as a replacement for "EtherNet/IP-2".
Brian Batke Brian Batke New contact added for port 44818 on 2008-02-01
EtherNet/IP-2 44818 tcp EtherNet/IP messaging Brian Batke Brian Batke New contact added for port 44818 on 2008-02-01 This entry is an alias to "EtherNet-IP-2". This entry is now historic, not usable for use with many common service discovery mechanisms.
EtherNet-IP-2 44818 udp EtherNet/IP messaging

IANA assigned this well-formed service name as a replacement for "EtherNet/IP-2".
Brian Batke Brian Batke New contact added for port 44818 on 2008-02-01
EtherNet/IP-2 44818 udp EtherNet/IP messaging Brian Batke Brian Batke New contact added for port 44818 on 2008-02-01 This entry is an alias to "EtherNet-IP-2". This entry is now historic, not usable for use with many common service discovery mechanisms.

Contact Information

Name Organization Contact URI Last Updated
Brian Batke eip.jsig&gmail.com
Brian Batke Chair of the EtherNet/IP System Architecture SIG babatke&ra.rockwell.com 2015-05-28
ODVA, Inc. babatke&ra.rockwell.com 2015-05-28