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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| msdp | 639 | tcp | MSDP | [Dino_Farinacci] | [Dino_Farinacci] | ||||||
| msdp | 639 | udp | MSDP | [Dino_Farinacci] | [Dino_Farinacci] | ||||||
| cert-initiator | 1639 | tcp | cert-initiator | ||||||||
| cert-initiator | 1639 | udp | cert-initiator | ||||||||
| aminet | 2639 | tcp | AMInet | [Alcorn_McBride_Inc] | [Alcorn_McBride_Inc] | ||||||
| aminet | 2639 | udp | AMInet | [Alcorn_McBride_Inc] | [Alcorn_McBride_Inc] | ||||||
| xap-ha | 3639 | tcp | Extensible Automation | [Mark_Harrison] | [Mark_Harrison] | 2002-11 | |||||
| xap-ha | 3639 | udp | Extensible Automation | [Mark_Harrison] | [Mark_Harrison] | 2002-11 | |||||
| ics | 5639 | tcp | Symantec Integrity Checking Service | [Symantec_Corp2] | [Danzhou_Liu] | 2012-05-07 | |||||
| 5639 | udp | Reserved | |||||||||
| metaedit-ws | 6390 | tcp | MetaEdit+ WebService API | [Steven_Kelly] | [Steven_Kelly] | 2007-11-12 | |||||
| metaedit-ws | 6390 | udp | MetaEdit+ WebService API | [Steven_Kelly] | [Steven_Kelly] | 2007-11-12 | |||||
| 6391-6399 | Unassigned | ||||||||||
| 6637-6639 | Unassigned | ||||||||||
| 9633-9639 | Unassigned | ||||||||||
| 38639-38799 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Alcorn_McBride_Inc] | Alcorn McBride Inc. | mailto:support&alcorn.com | ||
| [Danzhou_Liu] | Danzhou Liu | Symantec | mailto:Danzhou_Liu&symantec.com | 2012-05-07 |
| [Dino_Farinacci] | Dino Farinacci | mailto:dino&cisco.com | 2008-08-21 | |
| [Mark_Harrison] | Mark Harrison | mailto:Mark&xapautomation.org | 2002-11 | |
| [Steven_Kelly] | Steven Kelly | mailto:stevek&metacase.com | 2007-11-12 | |
| [Symantec_Corp2] | Symantec | mailto:info&symantec.com | 2012-05-07 |