Service Name and Transport Protocol Port Number Registry

Last Updated

  • 2026-10-13

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
rtsserv 2500 tcp Resource Tracking system server
rtsserv 2500 udp Resource Tracking system server
icl-twobase1 25000 tcp icl-twobase1 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase1 25000 udp icl-twobase1 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase2 25001 tcp icl-twobase2 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase2 25001 udp icl-twobase2 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase3 25002 tcp icl-twobase3 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase3 25002 udp icl-twobase3 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase4 25003 tcp icl-twobase4 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase4 25003 udp icl-twobase4 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase5 25004 tcp icl-twobase5 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase5 25004 udp icl-twobase5 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase6 25005 tcp icl-twobase6 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase6 25005 udp icl-twobase6 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase7 25006 tcp icl-twobase7 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase7 25006 udp icl-twobase7 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase8 25007 tcp icl-twobase8 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase8 25007 udp icl-twobase8 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase9 25008 tcp icl-twobase9 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase9 25008 udp icl-twobase9 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase10 25009 tcp icl-twobase10 J. A. (Tony) Sever J. A. (Tony) Sever
icl-twobase10 25009 udp icl-twobase10 J. A. (Tony) Sever J. A. (Tony) Sever

Contact Information

Name Contact URI Last Updated
J. A. (Tony) Sever J.A.Sever&bra0119.wins.icl.co.uk