Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2025-09-29
- Expert(s)
-
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, Jana Iyengar, 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
voxelstorm | 28200 | tcp | VoxelStorm game server | [VoxelStorm] | [Eugene_Hopkinson] | 2012-11-08 | |||||
voxelstorm | 28200 | udp | VoxelStorm game server | [VoxelStorm] | [Eugene_Hopkinson] | 2012-11-08 | |||||
28201-28239 | Unassigned | ||||||||||
autotrac-acp | 31020 | tcp | Autotrac ACP 245 | [Roberto_Jorge_Dino] | [Roberto_Jorge_Dino] | ||||||
31020 | udp | Reserved | |||||||||
lm-mon | 31620 | tcp | lm mon | [System_Administrator] | [System_Administrator] | 2003-06 | |||||
lm-mon | 31620 | udp | lm mon | [System_Administrator] | [System_Administrator] | 2003-06 | |||||
31950-32033 | Unassigned | ||||||||||
iracinghelper | 32034 | tcp | iRacing helper service | [Randy_Cassidy] | [Randy_Cassidy] | 2007-08-30 | |||||
iracinghelper | 32034 | udp | iRacing helper service | [Randy_Cassidy] | [Randy_Cassidy] | 2007-08-30 | |||||
32035-32248 | Unassigned | ||||||||||
38003-38200 | Unassigned | ||||||||||
galaxy7-data | 38201 | tcp | Galaxy7 Data Tunnel | [Tatham_Oddie] | [Tatham_Oddie] | 2002-09 | |||||
galaxy7-data | 38201 | udp | Galaxy7 Data Tunnel | [Tatham_Oddie] | [Tatham_Oddie] | 2002-09 | |||||
fairview | 38202 | tcp | Fairview Message Service | [Jim_Lyle] | [Jim_Lyle] | 2005-11 | Defined TXT keys: DevID=<device id>, DevType=<device type>, DevStat=<device status> | ||||
fairview | 38202 | udp | Fairview Message Service | [Jim_Lyle] | [Jim_Lyle] | 2005-11 | Defined TXT keys: DevID=<device id>, DevType=<device type>, DevStat=<device status> | ||||
agpolicy | 38203 | tcp | AppGate Policy Server | [Martin_Forssen] | [Martin_Forssen] | 2004-11 | |||||
agpolicy | 38203 | udp | AppGate Policy Server | [Martin_Forssen] | [Martin_Forssen] | 2004-11 | |||||
38204-38411 | Unassigned | ||||||||||
41112-41120 | Unassigned | ||||||||||
41798-42507 | Unassigned | Unauthorized Use Known on port 42000 | |||||||||
43192-43209 | Unassigned | ||||||||||
44124-44320 | Unassigned | ||||||||||
EtherNet-IP-2 | 44818 | tcp | EtherNet/IP messaging IANA assigned this well-formed service name as a replacement for "EtherNet/IP-2". |
[Brian_Batke_2] | [Brian_Batke_2] | New contact added for port 44818 on 2008-02-01 | |||||
EtherNet/IP-2 | 44818 | tcp | EtherNet/IP messaging | [Brian_Batke_2] | [Brian_Batke_2] | New contact added for port 44818 on 2008-02-01 This entry is an alias to "EtherNet-IP-2". This entry is now historic, not usable for use with many common service discovery mechanisms. | |||||
EtherNet-IP-2 | 44818 | udp | EtherNet/IP messaging IANA assigned this well-formed service name as a replacement for "EtherNet/IP-2". |
[Brian_Batke_2] | [Brian_Batke_2] | New contact added for port 44818 on 2008-02-01 | |||||
EtherNet/IP-2 | 44818 | udp | EtherNet/IP messaging | [Brian_Batke_2] | [Brian_Batke_2] | New contact added for port 44818 on 2008-02-01 This entry is an alias to "EtherNet-IP-2". This entry is now historic, not usable for use with many common service discovery mechanisms. | |||||
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. | |||
presence | Peer-to-peer messaging / Link-Local Messaging | [XMPP_Registrar] | [XMPP_Registrar] | Defined TXT keys: See http://www.xmpp.org/registrar/linklocal.html Note: Registration updated May 2007. Was formerly listed as "iChat AV" (Apple's IM client for Mac OS X) with TXT keys: txtvers, port.p2pj, phsh, vc, 1st, AIM, msg, status, last When first shipped in Mac OS X 10.2, iChat's peer-to-peer messaging protocol was created to solve the problem of serverless messaging between peers on the same link. However, there is nothing inherent in the protocol that limits it to being only link-local; it was simply an artifact of iChat in Mac OS X 10.2 using link-local Multicast DNS to discover peers. With the advent of Wide-Area DNS-SD, it is also possible to use iChat's peer-to-peer messaging between machines on different links. |
Contact Information
ID | Name | Organization | Contact URI | Last Updated |
---|---|---|---|---|
[Brian_Batke_2] | Brian Batke | mailto:eip.jsig&gmail.com | ||
[Eugene_Hopkinson] | Eugene Hopkinson | VoxelStorm | mailto:slowriot&voxelstorm.com | 2012-11-08 |
[IESG] | IESG | mailto:iesg&ietf.org | ||
[IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
[Jim_Lyle] | Jim Lyle | mailto:jim.lyle&siliconimage.com | 2005-11 | |
[Martin_Forssen] | Martin Forssen | mailto:maf&appgate.com | 2004-11 | |
[Randy_Cassidy] | Randy Cassidy | mailto:randy.cassidy&iracing.com | 2007-08-30 | |
[Roberto_Jorge_Dino] | Roberto Jorge Dino | mailto:roberto.dino&autotrac.com.br | ||
[System_Administrator] | System Administrator | mailto:sysadmin&silvaco.com | 2003-06 | |
[Tatham_Oddie] | Tatham Oddie | mailto:tatham&e-oddie.com | 2002-09 | |
[VoxelStorm] | VoxelStorm | mailto:slowriot&voxelstorm.com | 2012-11-08 | |
[XMPP_Registrar] | XMPP Registrar | mailto:registrar&xmpp.org |