Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-08-17
- 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
- [RFC6335]
- 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 process, as documented in [RFC6335]. Port numbers are assigned in various ways, based on three ranges: System Ports (0-1023), User Ports (1024-49151), and the Dynamic and/or Private Ports (49152-65535); the different uses of these ranges are described in [RFC6335]. According to Section 8.1.2 of [RFC6335], System Ports are assigned by the "IETF Review" or "IESG Approval" procedures described in [RFC8126]. User Ports are assigned by IANA using the "IETF Review" process, the "IESG Approval" process, or the "Expert Review" process, as per [RFC6335]. Dynamic Ports are not assigned. The registration procedures for service names and port numbers are described in [RFC6335]. Assigned ports both System and User ports SHOULD NOT be used without or prior to IANA registration. ************************************************************************ * PLEASE NOTE THE FOLLOWING: * * * * 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. * ************************************************************************
- Request an Assignment
-
[https://www.iana.org/protocols/apply]
- Available Formats
-

CSV
XML
HTML
Plain text
| Service Name | Port Number | Transport Protocol | Description | Assignee | Contact | Registration Date | Modification Date | Reference | Service Code | Unauthorized Use Reported | Assignment Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|
| keyserver | 584 | tcp | Key Server | [Gary_Howland] | [Gary_Howland] | ||||||
| keyserver | 584 | udp | Key Server | [Gary_Howland] | [Gary_Howland] | ||||||
| tn-tl-fd2 | 1584 | tcp | tn-tl-fd2 | [Ed_Kress] | [Ed_Kress] | ||||||
| tn-tl-fd2 | 1584 | udp | tn-tl-fd2 | [Ed_Kress] | [Ed_Kress] | ||||||
| cyaserv | 2584 | tcp | cyaserv | [Morgan_Jones] | [Morgan_Jones] | ||||||
| cyaserv | 2584 | udp | cyaserv | [Morgan_Jones] | [Morgan_Jones] | ||||||
| u-dbap | 3584 | tcp | U-DBase Access Protocol | [Bodo_Rueskamp] | [Bodo_Rueskamp] | 2002-08 | |||||
| u-dbap | 3584 | udp | U-DBase Access Protocol | [Bodo_Rueskamp] | [Bodo_Rueskamp] | 2002-08 | |||||
| pmip6-cntl | 5436 | udp | pmip6-cntl | [RFC5844] | |||||||
| pmip6-data | 5437 | udp | pmip6-data | [RFC5844] | |||||||
| bis-web | 5584 | tcp | BeInSync-Web | [Adi_Ruppin] | [Adi_Ruppin] | 2005-08 | |||||
| bis-web | 5584 | udp | BeInSync-Web | [Adi_Ruppin] | [Adi_Ruppin] | 2005-08 | |||||
| 5821-5840 | Unassigned | ||||||||||
| shiprush-d-ch | 5841 | tcp | Z-firm ShipRush interface for web access and bidirectional data | [Z-Firm_LLC] | [Rafael_Zimberoff] | 2014-08-22 | |||||
| 5841 | udp | Reserved | |||||||||
| reversion | 5842 | tcp | Reversion Backup/Restore | [Pincoder_Diagnostics_Inc] | [Craig_Nelson] | 2011-09-26 | 2022-10-12 | ||||
| 5842 | udp | Reserved | |||||||||
| 5843-5858 | Unassigned | ||||||||||
| 6584-6587 | Unassigned | ||||||||||
| x510 | 9877 | tcp | The X.510 wrapper protocol | [ITU_TSB_ITU-T_Study_Group_17] | [Erik_Andersen] | 2019-09-30 | [ITU-T X.510 / ISO/IEC 9584-11] |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Adi_Ruppin] | Adi Ruppin | mailto:adi.ruppin&data-pod.com | 2005-08 | |
| [Bodo_Rueskamp] | Bodo Rueskamp | mailto:iana+spam&pinda.de | 2020-06-04 | |
| [Craig_Nelson] | Craig Nelson | Pincoder Diagnostics Inc. | mailto:craig&pincoder.ca | 2022-10-12 |
| [Ed_Kress] | Ed Kress | mailto:eskress&thinknet.com | ||
| [Erik_Andersen] | Erik Andersen | mailto:era&x500.eu | 2019-08-13 | |
| [Gary_Howland] | Gary Howland | mailto:gary&systemics.com | ||
| [ITU_TSB_ITU-T_Study_Group_17] | ITU/TSB (ITU-T Study Group 17) | mailto:tsbsg17&itu.int | 2019-09-30 | |
| [Morgan_Jones] | Morgan Jones | mailto:mwj&cyasolutions.com | ||
| [Pincoder_Diagnostics_Inc] | Pincoder Diagnostics Inc. | mailto:craig&pincoder.ca | 2022-10-12 | |
| [Rafael_Zimberoff] | Rafael Zimberoff | mailto:rafael&zfirmllc.com | 2003-11 | |
| [Z-Firm_LLC] | Z-Firm LLC | mailto:rafael&zfirmllc.com | 2014-08-22 |