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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ulpnet | 483 | tcp | ulpnet | [Kevin_Mooney] | [Kevin_Mooney] | ||||||
| ulpnet | 483 | udp | ulpnet | [Kevin_Mooney] | [Kevin_Mooney] | ||||||
| afs | 1483 | tcp | AFS License Manager | [Michael_R_Pizolato] | [Michael_R_Pizolato] | ||||||
| afs | 1483 | udp | AFS License Manager | [Michael_R_Pizolato] | [Michael_R_Pizolato] | ||||||
| ttc | 2483 | tcp | Oracle TTC | ||||||||
| ttc | 2483 | udp | Oracle TTC | ||||||||
| slim-devices | 3483 | tcp | Slim Devices Protocol | [Sean_Adams] | [Sean_Adams] | 2002-05 | |||||
| slim-devices | 3483 | udp | Slim Devices Protocol | [Sean_Adams] | [Sean_Adams] | 2002-05 | |||||
| 4481-4483 | Unassigned | ||||||||||
| 4828-4836 | Unassigned | ||||||||||
| varadero-0 | 4837 | tcp | Varadero-0 | ||||||||
| varadero-0 | 4837 | udp | Varadero-0 | ||||||||
| varadero-1 | 4838 | tcp | Varadero-1 | ||||||||
| varadero-1 | 4838 | udp | Varadero-1 | ||||||||
| varadero-2 | 4839 | tcp | Varadero-2 | [Carlos_Arteaga] | [Carlos_Arteaga] | ||||||
| varadero-2 | 4839 | udp | Varadero-2 | [Carlos_Arteaga] | [Carlos_Arteaga] | ||||||
| SunVTS-RMI | 6483 | tcp | SunVTS RMI | [Sumit_Arora] | [Sumit_Arora] | 2007-06 | |||||
| SunVTS-RMI | 6483 | udp | SunVTS RMI | [Sumit_Arora] | [Sumit_Arora] | 2007-06 | |||||
| apm-link | 32483 | tcp | Access Point Manager Link | [Tony_Diodato] | [Tony_Diodato] | 2005-08 | |||||
| apm-link | 32483 | udp | Access Point Manager Link | [Tony_Diodato] | [Tony_Diodato] | 2005-08 | |||||
| gdrive-sync | 37483 | tcp | Google Drive Sync | [Google_Inc] | [Jason_Schiller] | 2013-02-01 | 2015-07-31 | ||||
| 37483 | udp | Reserved | |||||||||
| brski-reg-cmp | tcp | Bootstrapping Remote Secure Key Infrastructure registrar with CMP capabilities according to the Lightweight CMP Profile (LCMPP) [RFC9483] | [IESG] | [IETF_Chair] | 2024-09-23 | [RFC9733] | Defined TXT keys: None |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Carlos_Arteaga] | Carlos Arteaga | mailto:carteaga&abacoinc.com | ||
| [Google_Inc] | Google Inc. | mailto:numbers&google.com | 2015-07-31 | |
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [Jason_Schiller] | Jason Schiller | Google Inc. | mailto:jschiller&google.com | 2015-07-31 |
| [Kevin_Mooney] | Kevin Mooney | mailto:kevinm&bfs.unibol.com | ||
| [Michael_R_Pizolato] | Michael R. Pizolato | mailto:michael&afs.com | ||
| [Sean_Adams] | Sean Adams | mailto:sean&slimdevices.com | 2002-05 | |
| [Sumit_Arora] | Sumit Arora | mailto:sumit.arora&sun.com | 2007-06 | |
| [Tony_Diodato] | Tony Diodato | mailto:tdiodato&cyprx.com | 2005-08 |