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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| xfr | 682 | tcp | XFR | [Noah_Paul_2] | [Noah_Paul_2] | ||||||
| xfr | 682 | udp | XFR | [Noah_Paul_2] | [Noah_Paul_2] | ||||||
| lanyon-lantern | 1682 | tcp | lanyon-lantern | [Robin_Lewis] | [Robin_Lewis] | ||||||
| lanyon-lantern | 1682 | udp | lanyon-lantern | [Robin_Lewis] | [Robin_Lewis] | ||||||
| 2682 | Removed | 2002-04-30 | |||||||||
| cas-mapi | 3682 | tcp | EMC SmartPackets-MAPI | [Koen_Schoofs] | [Koen_Schoofs] | 2003-01 | |||||
| cas-mapi | 3682 | udp | EMC SmartPackets-MAPI | [Koen_Schoofs] | [Koen_Schoofs] | 2003-01 | |||||
| finisar | 4682 | tcp | finisar | [Christina_Mercier] | [Christina_Mercier] | 2005-08 | |||||
| finisar | 4682 | udp | finisar | [Christina_Mercier] | [Christina_Mercier] | 2005-08 | |||||
| 5682 | tcp | Reserved | |||||||||
| brightcore | 5682 | udp | BrightCore control & data transfer exchange | [Marko_Bjelac] | [Marko_Bjelac] | 2010-06-10 | |||||
| 7681-7682 | Unassigned | ||||||||||
| 39682-39999 | Unassigned |
Contact Information
| ID | Name | Contact URI | Last Updated |
|---|---|---|---|
| [Christina_Mercier] | Christina Mercier | mailto:christina.mercier&finisar.com | 2005-08 |
| [Koen_Schoofs] | Koen Schoofs | mailto:schoofs_koen&emc.com | 2003-01 |
| [Marko_Bjelac] | Marko Bjelac | mailto:marko.bjelac&elma.hr | 2010-06-10 |
| [Noah_Paul_2] | Noah Paul | mailto:noahp&ultranet.com | |
| [Robin_Lewis] | Robin Lewis | mailto:robin.lewis&lanyon.com |