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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| netviewdm1 | 729 | tcp | IBM NetView DM/6000 Server/Client | ||||||||
| netviewdm1 | 729 | udp | IBM NetView DM/6000 Server/Client | ||||||||
| netviewdm2 | 730 | tcp | IBM NetView DM/6000 send/tcp | ||||||||
| netviewdm2 | 730 | udp | IBM NetView DM/6000 send/tcp | ||||||||
| netviewdm3 | 731 | tcp | IBM NetView DM/6000 receive/tcp | [Philippe_Binet] | [Philippe_Binet] | ||||||
| netviewdm3 | 731 | udp | IBM NetView DM/6000 receive/tcp | [Philippe_Binet] | [Philippe_Binet] | ||||||
| x11 | 6000-6063 | tcp | X Window System | [Stephen_Gildea] | [Stephen_Gildea] | Known Unauthorized Use on port 6003 | |||||
| x11 | 6000-6063 | udp | X Window System | [Stephen_Gildea] | [Stephen_Gildea] | Known Unauthorized Use on port 6003 | |||||
| fmsas | 16000 | tcp | Administration Server Access | [Mark_Davidson] | [Mark_Davidson] | 2010-10-06 | Known Unauthorized Use on port 16000 | ||||
| 16000 | udp | Reserved | Known Unauthorized Use on port 16000 | ||||||||
| quake | 26000 | tcp | quake | [Yasunari_Gon_Yamasit] | [Yasunari_Gon_Yamasit] | ||||||
| quake | 26000 | udp | quake | [Yasunari_Gon_Yamasit] | [Yasunari_Gon_Yamasit] | ||||||
| 35358-36000 | Unassigned |
Contact Information
| ID | Name | Contact URI | Last Updated |
|---|---|---|---|
| [Mark_Davidson] | Mark Davidson | mailto:mark_davidson&filemaker.com | 2010-10-06 |
| [Philippe_Binet] | Philippe Binet | mailto:phbinet&vnet.ibm.com | |
| [Stephen_Gildea] | Stephen Gildea | mailto:gildea&lcs.mit.edu | |
| [Yasunari_Gon_Yamasit] | Yasunari Gon Yamasita | mailto:yamasita&omronsoft.co.jp |