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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| isnetserv | 48128 | udp | Image Systems Network Services | [Bengt_Gustafsson] | [Bengt_Gustafsson] | 2006-05 | |||||
| blp5 | 48129 | tcp | Bloomberg locator | [Albert_Hou] | [Albert_Hou] | 2006-05 | |||||
| blp5 | 48129 | udp | Bloomberg locator | [Albert_Hou] | [Albert_Hou] | 2006-05 | |||||
| 48130-48555 | Unassigned | ||||||||||
| com-bardac-dw | 48556 | tcp | com-bardac-dw | [Nicholas_J_Howes] | [Nicholas_J_Howes] | ||||||
| com-bardac-dw | 48556 | udp | com-bardac-dw | [Nicholas_J_Howes] | [Nicholas_J_Howes] | ||||||
| 48557-48618 | Unassigned | ||||||||||
| iqobject | 48619 | tcp | iqobject | [Bjorn_de_Bonnenfant] | [Bjorn_de_Bonnenfant] | 2003-11 | |||||
| iqobject | 48619 | udp | iqobject | [Bjorn_de_Bonnenfant] | [Bjorn_de_Bonnenfant] | 2003-11 | |||||
| 48620-48652 | Unassigned | ||||||||||
| robotraconteur | 48653 | tcp | Robot Raconteur transport | [Wason_Technology_LLC] | [John_Wason] | 2014-01-27 | |||||
| robotraconteur | 48653 | udp | Robot Raconteur transport | [Wason_Technology_LLC] | [John_Wason] | 2014-01-27 | |||||
| 48654-48999 | Unassigned | ||||||||||
| 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 | ||||
| est-coaps | udp | EST over secure CoAP (EST-coaps) | [Toerless_Eckert_3] | [Toerless_Eckert_3] | 2022-05-03 | 2022-05-04 | [RFC9148]. Defined TXT keys: None | ||||
| lxi | LXI | [Nick_Barendt_2] | [Nick_Barendt_2] | Defined TXT keys: txtvers, *IDN?=<response defined by IEEE 488; e.g., manufacturer, model, serial number, version> | |||||||
| scpi-raw | IEEE 488.2 (SCPI) Socket | [Nick_Barendt_3] | [Nick_Barendt_3] | Defined TXT keys: None | |||||||
| scpi-telnet | IEEE 488.2 (SCPI) Telnet | [Nick_Barendt_3] | [Nick_Barendt_3] | Defined TXT keys: None |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Albert_Hou] | Albert Hou | mailto:ahou1&bloomberg.com | 2006-05 | |
| [Bengt_Gustafsson] | Bengt Gustafsson | mailto:bengt.gustafsson&imagesystems.se | 2006-05 | |
| [Bjorn_de_Bonnenfant] | Bjorn de Bonnenfant | mailto:bdeb&iqobject.com | 2003-11 | |
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [John_Wason] | John Wason | Wason Technology, LLC | mailto:wason&wasontech.com | 2014-01-27 |
| [Nicholas_J_Howes] | Nicholas J Howes | mailto:nick&ghostwood.org | ||
| [Nick_Barendt_2] | Nick Barendt | mailto:nbarendt&vxitech.com | ||
| [Nick_Barendt_3] | Nick Barendt | mailto:nbarendt&vxitech.com | ||
| [Toerless_Eckert_3] | Toerless Eckert | mailto:tte&cs.fau.de | 2022-05-03 | |
| [Wason_Technology_LLC] | Wason Technology, LLC | mailto:wason&wasontech.com | 2014-01-27 |