Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-02
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ns | 760 | tcp | |||||||||
| ns | 760 | udp | |||||||||
| www-ldap-gw | 1760 | tcp | www-ldap-gw | [Nick_Emery] | [Nick_Emery] | ||||||
| www-ldap-gw | 1760 | udp | www-ldap-gw | [Nick_Emery] | [Nick_Emery] | ||||||
| sabams | 2760 | tcp | Saba MS | [Davoud_Maha] | [Davoud_Maha] | ||||||
| sabams | 2760 | udp | Saba MS | [Davoud_Maha] | [Davoud_Maha] | ||||||
| adtempusclient | 3760 | tcp | adTempus Client | [Bill_Wingate] | [Bill_Wingate] | 2003-05 | |||||
| adtempusclient | 3760 | udp | adTEmpus Client | [Bill_Wingate] | [Bill_Wingate] | 2003-05 | |||||
| 7589-7605 | Unassigned | ||||||||||
| mipi-debug | 7606 | tcp | MIPI Alliance Debug | [MIPI_Alliance] | [Peter_Lefkin] | 2016-02-26 | |||||
| mipi-debug | 7606 | udp | MIPI Alliance Debug | [MIPI_Alliance] | [Peter_Lefkin] | 2016-02-26 | |||||
| 7607-7623 | Unassigned | ||||||||||
| 37484-37600 | Unassigned | ||||||||||
| eftp | 37601 | tcp | Epipole File Transfer Protocol | [Epipole_Limited] | [Colin_Buchanan] | 2014-11-13 | |||||
| 37601 | udp | Reserved | |||||||||
| 37602-37653 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Bill_Wingate] | Bill Wingate | mailto:bill.wingate&arcanadev.com | 2003-05 | |
| [Colin_Buchanan] | Colin Buchanan | Epipole Limited | mailto:colin&epipole.com | 2014-11-13 |
| [Davoud_Maha] | Davoud Maha | mailto:dmaha&saba.com | ||
| [Epipole_Limited] | Epipole Limited | mailto:info&epipole.com | 2014-11-13 | |
| [MIPI_Alliance] | Mipi Alliance | mailto:secretary&mipi.org | 2016-02-26 | |
| [Nick_Emery] | Nick Emery | mailto:Nick.Emery&altavista.digital.com | ||
| [Peter_Lefkin] | Peter Lefkin | mailto:peter.lefkin&mipi.org | 2016-02-26 |