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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| fatserv | 347 | tcp | Fatmen Server | ||||||||
| fatserv | 347 | udp | Fatmen Server | ||||||||
| bbn-mmc | 1347 | tcp | multi media conferencing | ||||||||
| bbn-mmc | 1347 | udp | multi media conferencing | ||||||||
| redstorm-find | 2347 | tcp | Game Announcement and Location IANA assigned this well-formed service name as a replacement for "redstorm_find". |
||||||||
| redstorm_find | 2347 | tcp | Game Announcement and Location | This entry is an alias to "redstorm-find". This entry is now historic, not usable for use with many common service discovery mechanisms. | |||||||
| redstorm-find | 2347 | udp | Game Announcement and Location IANA assigned this well-formed service name as a replacement for "redstorm_find". |
||||||||
| redstorm_find | 2347 | udp | Game Announcement and Location | This entry is an alias to "redstorm-find". This entry is now historic, not usable for use with many common service discovery mechanisms. | |||||||
| phoenix-rpc | 3347 | tcp | Phoenix RPC | [Ian_Anderson] | [Ian_Anderson] | ||||||
| phoenix-rpc | 3347 | udp | Phoenix RPC | [Ian_Anderson] | [Ian_Anderson] | ||||||
| jt400 | 3470 | tcp | jt400 | ||||||||
| jt400 | 3470 | udp | jt400 | ||||||||
| jt400-ssl | 3471 | tcp | jt400-ssl | [Clifton_Nock] | [Clifton_Nock] | ||||||
| jt400-ssl | 3471 | udp | jt400-ssl | [Clifton_Nock] | [Clifton_Nock] | ||||||
| jaugsremotec-1 | 3472 | tcp | JAUGS N-G Remotec 1 | ||||||||
| jaugsremotec-1 | 3472 | udp | JAUGS N-G Remotec 1 | ||||||||
| jaugsremotec-2 | 3473 | tcp | JAUGS N-G Remotec 2 | [Steven_B_Cliff] | [Steven_B_Cliff] | 2002-04 | |||||
| jaugsremotec-2 | 3473 | udp | JAUGS N-G Remotec 2 | [Steven_B_Cliff] | [Steven_B_Cliff] | 2002-04 | |||||
| ttntspauto | 3474 | tcp | TSP Automation | [Arnie_Koster] | [Arnie_Koster] | 2002-04 | |||||
| ttntspauto | 3474 | udp | TSP Automation | [Arnie_Koster] | [Arnie_Koster] | 2002-04 | |||||
| genisar-port | 3475 | tcp | Genisar Comm Port | [Candace_Niccolson] | [Candace_Niccolson] | 2002-04 | |||||
| genisar-port | 3475 | udp | Genisar Comm Port | [Candace_Niccolson] | [Candace_Niccolson] | 2002-04 | |||||
| nppmp | 3476 | tcp | NVIDIA Mgmt Protocol | [Gilbert_Yeung] | [Gilbert_Yeung] | 2002-04 | |||||
| nppmp | 3476 | udp | NVIDIA Mgmt Protocol | [Gilbert_Yeung] | [Gilbert_Yeung] | 2002-04 | |||||
| ecomm | 3477 | tcp | eComm link port | [Thomas_Soerensen] | [Thomas_Soerensen] | 2002-04 | |||||
| ecomm | 3477 | udp | eComm link port | [Thomas_Soerensen] | [Thomas_Soerensen] | 2002-04 | |||||
| stun | 3478 | tcp | Session Traversal Utilities for NAT (STUN) port | [IESG] | [IETF_Chair] | 2019-03-28 | [RFC8489] | ||||
| stun | 3478 | udp | Session Traversal Utilities for NAT (STUN) port | [IESG] | [IETF_Chair] | 2019-03-28 | [RFC8489] | ||||
| turn | 3478 | tcp | TURN over TCP | 2019-08-02 | [RFC8656] | ||||||
| turn | 3478 | udp | TURN over UDP | 2019-08-02 | [RFC8656] | ||||||
| stun-behavior | 3478 | tcp | STUN Behavior Discovery over TCP | [RFC5780] | |||||||
| stun-behavior | 3478 | udp | STUN Behavior Discovery over UDP | [RFC5780] | |||||||
| twrpc | 3479 | tcp | 2Wire RPC | [Wire_IANA_Contact] | [Wire_IANA_Contact] | 2002-04 | |||||
| twrpc | 3479 | udp | 2Wire RPC | [Wire_IANA_Contact] | [Wire_IANA_Contact] | 2002-04 | |||||
| lansurveyor | 4347 | tcp | LAN Surveyor | [Michael_Swan] | [Michael_Swan] | ||||||
| lansurveyor | 4347 | udp | LAN Surveyor | [Michael_Swan] | [Michael_Swan] | ||||||
| gnutella-rtr | 6347 | tcp | gnutella-rtr | [Serguei_Osokine] | [Serguei_Osokine] | ||||||
| gnutella-rtr | 6347 | udp | gnutella-rtr | [Serguei_Osokine] | [Serguei_Osokine] | ||||||
| 9347-9373 | Unassigned | ||||||||||
| wibukey | 22347 | tcp | WibuKey Standard WkLan | [Wolfgang_Voelker] | [Wolfgang_Voelker] | 2007-06 | |||||
| wibukey | 22347 | udp | WibuKey Standard WkLan | [Wolfgang_Voelker] | [Wolfgang_Voelker] | 2007-06 |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Arnie_Koster] | Arnie Koster | mailto:akoster&teltone.com | 2002-04 | |
| [Candace_Niccolson] | Candace Niccolson | mailto:cniccolson&genisar.com | 2002-04 | |
| [Clifton_Nock] | Clifton Nock | mailto:cnock&us.ibm.com | ||
| [Gilbert_Yeung] | Gilbert Yeung | mailto:gyeung&nvidia.com | 2002-04 | |
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [Ian_Anderson] | Ian Anderson | mailto:ian_anderson&phoenix.com | ||
| [Michael_Swan] | Michael Swan | mailto:swan&neon.com | 2004-04 | |
| [Serguei_Osokine] | Serguei Osokine | mailto:osokin¶graph.com | ||
| [Steven_B_Cliff] | Steven B. Cliff | mailto:scliff&remotec-andros.com | 2003-07 | |
| [Thomas_Soerensen] | Thomas Soerensen | mailto:thomassoerensen&stofanet.dk | 2002-04 | |
| [Wire_IANA_Contact] | 2Wire IANA Contact | mailto:iana&2wire.com | 2002-04 | |
| [Wolfgang_Voelker] | Wolfgang Voelker | mailto:wolfgang.voelker&wibu.com | 2007-06 |