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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ipp | 631 | tcp | IPP (Internet Printing Protocol) | [IESG] | [IETF_Chair] | 2018-07-06 | [RFC8011] | Defined TXT keys: See BonjourPrinting.pdf. | |||
| ipp | 631 | udp | IPP (Internet Printing Protocol) | [IESG] | [IETF_Chair] | 2018-07-06 | [RFC8011] | Defined TXT keys: See BonjourPrinting.pdf. | |||
| ipps | 631 | tcp | Internet Printing Protocol over HTTPS | [IESG] | [IETF_Chair] | 2018-07-06 | [RFC8011] | ||||
| visitview | 1631 | tcp | Visit view | [Tom_Whittaker] | [Tom_Whittaker] | ||||||
| visitview | 1631 | udp | Visit view | [Tom_Whittaker] | [Tom_Whittaker] | ||||||
| sitaradir | 2631 | tcp | Sitara Dir | [Manickam_R_Sridhar] | [Manickam_R_Sridhar] | ||||||
| sitaradir | 2631 | udp | Sitara Dir | [Manickam_R_Sridhar] | [Manickam_R_Sridhar] | ||||||
| cs-services | 3631 | tcp | C&S Web Services Port | [Computer_Software_Gm] | [Computer_Software_Gm] | 2002-10 | |||||
| cs-services | 3631 | udp | C&S Web Services Port | [Computer_Software_Gm] | [Computer_Software_Gm] | 2002-10 | |||||
| pcanywheredata | 5631 | tcp | pcANYWHEREdata | [Jon_Rosarky] | [Jon_Rosarky] | ||||||
| pcanywheredata | 5631 | udp | pcANYWHEREdata | [Jon_Rosarky] | [Jon_Rosarky] | ||||||
| 6307-6314 | Unassigned | ||||||||||
| scup | 6315 | tcp | Sensor Control Unit Protocol | [Sven_Kopacz] | [Sven_Kopacz] | 2010-09-01 | |||||
| scup-disc | 6315 | udp | Sensor Control Unit Protocol Discovery Protocol | [Sven_Kopacz] | [Sven_Kopacz] | 2010-09-01 | |||||
| abb-escp | 6316 | tcp | Ethernet Sensor Communications Protocol | [Jaime_Antolin] | [Jaime_Antolin] | 2008-09-25 | |||||
| abb-escp | 6316 | udp | Ethernet Sensor Communications Protocol | [Jaime_Antolin] | [Jaime_Antolin] | 2008-09-25 | |||||
| nav-data-cmd | 6317 | tcp | Navtech Radar Sensor Data Command | [Navtech_Radar_Ltd] | [Guy_Avery] | 2013-02-20 | |||||
| nav-data | 6317 | udp | Navtech Radar Sensor Data | [Navtech_Radar_Ltd] | [Guy_Avery] | 2013-02-20 | |||||
| iona-data | 6318 | tcp | IONA Measurement and control data | [Insphere_Ltd] | [Guy_Avery_2] | 2024-07-01 | |||||
| 6318 | udp | Reserved | |||||||||
| 6319 | Unassigned | ||||||||||
| 6631 | Unassigned | 2004-05-28 | |||||||||
| tesla-sys-msg | 7631 | tcp | TESLA System Messaging | [Andy_Perreault] | [Andy_Perreault] | 2010-03-31 | |||||
| 7631 | udp | Reserved | |||||||||
| peocoll | 9631 | tcp | Peovica Collector | [Adrian_Hungate] | [Adrian_Hungate] | 2009-09-14 | |||||
| 9631 | udp | Reserved | |||||||||
| printopia | 10631 | tcp | Printopia Serve | [Decisive_Tactics_Inc] | [Chris_Kent] | 2011-10-24 | 2015-04-09 | ||||
| 10631 | udp | Reserved | |||||||||
| pduncs | 16310 | tcp | Policy Distribute, Update Notification | [Diane_I_Shannon] | [Diane_I_Shannon] | 2006-08 | |||||
| pduncs | 16310 | udp | Policy Distribute, Update Notification | [Diane_I_Shannon] | [Diane_I_Shannon] | 2006-08 | |||||
| pdefmns | 16311 | tcp | Policy definition and update management | [Diane_I_Shannon] | [Diane_I_Shannon] | 2007-04 | |||||
| pdefmns | 16311 | udp | Policy definition and update management | [Diane_I_Shannon] | [Diane_I_Shannon] | 2007-04 | |||||
| 16312-16359 | Unassigned |