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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| tunnel | 604 | tcp | TUNNEL | [RFC3620] | |||||||
| tunnel | 604 | udp | TUNNEL | [RFC3620] | |||||||
| sco-websrvrmgr | 620 | tcp | SCO WebServer Manager | [Christopher_Durham] | [Christopher_Durham] | ||||||
| sco-websrvrmgr | 620 | udp | SCO WebServer Manager | [Christopher_Durham] | [Christopher_Durham] | ||||||
| faxportwinport | 1620 | tcp | faxportwinport | [Chris_Wells] | [Chris_Wells] | ||||||
| faxportwinport | 1620 | udp | faxportwinport | [Chris_Wells] | [Chris_Wells] | ||||||
| lpsrecommender | 2620 | tcp | LPSRecommender | [Pritham_Shetty_2] | [Pritham_Shetty_2] | ||||||
| lpsrecommender | 2620 | udp | LPSRecommender | [Pritham_Shetty_2] | [Pritham_Shetty_2] | ||||||
| ep-pcp | 3620 | tcp | EPSON Projector Control Port | ||||||||
| ep-pcp | 3620 | udp | EPSON Projector Control Port | ||||||||
| 4607-4620 | Unassigned | ||||||||||
| lm-x | 6200 | tcp | LM-X License Manager by X-Formation | [Henrik_Goldman] | [Henrik_Goldman] | 2006-10 | Known Unauthorized Use on port 6200 | ||||
| lm-x | 6200 | udp | LM-X License Manager by X-Formation | [Henrik_Goldman] | [Henrik_Goldman] | 2006-10 | Known Unauthorized Use on port 6200 | ||||
| 6201 | tcp | Reserved | |||||||||
| thermo-calc | 6201 | udp | Management of service nodes in a processing grid for thermodynamic calculations | [Thermo-Calc_Software] | [Thomas_Revesz] | 2012-06-28 | |||||
| 6202-6208 | Unassigned | ||||||||||
| qmtps | 6209 | tcp | QMTP over TLS | [FEHCom] | [Erwin_Hoffmann] | 2015-01-09 | |||||
| qmtps | 6209 | udp | QMTP over TLS | [FEHCom] | [Erwin_Hoffmann] | 2015-01-09 | |||||
| kftp-data | 6620 | tcp | Kerberos V5 FTP Data | [Robert_J_Scott] | [Robert_J_Scott] | 2005-08 | |||||
| kftp-data | 6620 | udp | Kerberos V5 FTP Data | [Robert_J_Scott] | [Robert_J_Scott] | 2005-08 | |||||
| 16620-16664 | Unassigned | ||||||||||
| 26134-26207 | Unassigned | ||||||||||
| wnn6-ds | 26208 | tcp | wnn6-ds | [Yasunari_Gon_Yamasit] | [Yasunari_Gon_Yamasit] | ||||||
| wnn6-ds | 26208 | udp | wnn6-ds | [Yasunari_Gon_Yamasit] | [Yasunari_Gon_Yamasit] | ||||||
| 26209-26256 | Unassigned | ||||||||||
| lm-mon | 31620 | tcp | lm mon | [System_Administrator] | [System_Administrator] | 2003-06 | |||||
| lm-mon | 31620 | udp | lm mon | [System_Administrator] | [System_Administrator] | 2003-06 | |||||
| 48620-48652 | Unassigned | ||||||||||
| jmap | tcp | JSON Meta Application Protocol | [IESG] | [IETF_Chair] | 2016-01-22 | 2019-07-16 | [RFC8620] | This service name was previously assigned under the name "JSON Mail Access Protocol". This has been de-assigned and re-assigned with the approval of the previous assignee. |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Chris_Wells] | Chris Wells | mailto:chris_wells&lansource.com | ||
| [Christopher_Durham] | Christopher Durham | mailto:chrisdu&sco.com | ||
| [Erwin_Hoffmann] | Erwin Hoffmann | FEHCom | mailto:feh&fehcom.de | 2015-01-09 |
| [FEHCom] | FEHCom | mailto:feh&fehcom.de | 2015-01-09 | |
| [Henrik_Goldman] | Henrik Goldman | mailto:hg&x-formation.com | 2006-10 | |
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [Pritham_Shetty_2] | Pritham Shetty | mailto:pritham&andromedia.com | ||
| [Robert_J_Scott] | Robert J. Scott | mailto:rob&hpcmo.hpc.mil | 2005-08 | |
| [System_Administrator] | System Administrator | mailto:sysadmin&silvaco.com | 2003-06 | |
| [Thermo-Calc_Software] | Thermo-Calc Software AB | mailto:thomasr&thermocalc.se | 2012-06-28 | |
| [Thomas_Revesz] | Thomas Revesz | Thermo-Calc Software AB | mailto:thomasr&thermocalc.se | 2012-06-28 |
| [Yasunari_Gon_Yamasit] | Yasunari Gon Yamasita | mailto:yamasita&omronsoft.co.jp |