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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| dasp | 439 | tcp | dasp | [Thomas_Obermair] | [Thomas_Obermair] | ||||||
| dasp | 439 | udp | dasp | [Thomas_Obermair] | [Thomas_Obermair] | ||||||
| eicon-x25 | 1439 | tcp | Eicon X25/SNA Gateway | ||||||||
| eicon-x25 | 1439 | udp | Eicon X25/SNA Gateway | ||||||||
| sybasedbsynch | 2439 | tcp | SybaseDBSynch | [Dave_Neudoerffer] | [Dave_Neudoerffer] | ||||||
| sybasedbsynch | 2439 | udp | SybaseDBSynch | [Dave_Neudoerffer] | [Dave_Neudoerffer] | ||||||
| hri-port | 3439 | tcp | HRI Interface Port | [John_Fayos] | [John_Fayos] | 2002-03 | |||||
| hri-port | 3439 | udp | HRI Interface Port | [John_Fayos] | [John_Fayos] | 2002-03 | |||||
| wiegand | 4390 | tcp | Physical Access Control | [Scott_Guthery_2] | [Scott_Guthery_2] | 2008-08-25 | |||||
| wiegand | 4390 | udp | Physical Access Control | [Scott_Guthery_2] | [Scott_Guthery_2] | 2008-08-25 | |||||
| apwi-imserver | 4391 | tcp | American Printware IMServer Protocol | [Lech_Lakomy] | [Lech_Lakomy] | 2009-02-12 | |||||
| 4391 | udp | Reserved | |||||||||
| apwi-rxserver | 4392 | tcp | American Printware RXServer Protocol | [Lech_Lakomy] | [Lech_Lakomy] | 2009-02-12 | |||||
| 4392 | udp | Reserved | |||||||||
| apwi-rxspooler | 4393 | tcp | American Printware RXSpooler Protocol | [Lech_Lakomy] | [Lech_Lakomy] | 2009-02-12 | |||||
| 4393 | udp | Reserved | |||||||||
| 4394 | tcp | Reserved | |||||||||
| apwi-disc | 4394 | udp | American Printware Discovery | [Lech_Lakomy] | [Lech_Lakomy] | 2009-02-12 | |||||
| omnivisionesx | 4395 | tcp | OmniVision communication for Virtual environments | [Vacquier_Serge] | [Vacquier_Serge] | 2009-02-12 | |||||
| omnivisionesx | 4395 | udp | OmniVision communication for Virtual environments | [Vacquier_Serge] | [Vacquier_Serge] | 2009-02-12 | |||||
| fly | 4396 | tcp | Fly Object Space | [Nigel_Warren] | [Nigel_Warren] | 2009-02-12 | |||||
| 4396 | udp | Reserved | |||||||||
| 4397-4399 | Unassigned | ||||||||||
| 6433-6439 | Unassigned | ||||||||||
| bngsync | 10439 | udp | BalanceNG session table synchronization protocol | [Inlab_Software_GmbH] | [Thomas_G._Obermair] | 2014-05-02 | |||||
| 10439 | tcp | Reserved | |||||||||
| eq3-update | 43439 | tcp | EQ3 firmware update | [eQ-3_Entwicklung_GmbH] | [Tido_de_Vries] | 2012-02-10 | 2014-05-09 | ||||
| eq3-config | 43439 | udp | EQ3 discovery and configuration | [eQ-3_Entwicklung_GmbH] | [Tido_de_Vries] | 2012-02-10 | 2014-05-09 |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Dave_Neudoerffer] | Dave Neudoerffer | mailto:Dave.Neudoerffer&ianywhere.com | ||
| [eQ-3_Entwicklung_GmbH] | eQ-3 Entwicklung GmbH | mailto:ports&entwicklung.eq-3.de | 2018-02-28 | |
| [Inlab_Software_GmbH] | Inlab Software GmbH | mailto:info&inlab.de | 2014-05-02 | |
| [John_Fayos] | John Fayos | mailto:john.fayos&criticallink.com | 2002-03 | |
| [Lech_Lakomy] | Lech Lakomy | mailto:llakomy&apwi.com | 2009-02-12 | |
| [Nigel_Warren] | Nigel Warren | mailto:info&flyobjectspace.com | 2009-02-12 | |
| [Scott_Guthery_2] | Scott Guthery | mailto:sguthery&hidcorp.com | 2008-08-25 | |
| [Thomas_G._Obermair] | Thomas G. Obermair | Inlab Software GmbH | mailto:thomas.obermair&inlab.de | 2014-05-02 |
| [Thomas_Obermair] | Thomas Obermair | mailto:tommy&inlab.m.eunet.de | ||
| [Tido_de_Vries] | Tido de Vries | eQ-3 Entwicklung GmbH | mailto:tido.devries&entwicklung.eq-3.de | 2018-02-28 |
| [Vacquier_Serge] | Vacquier Serge | mailto:vacquier&systar.fr | 2009-02-12 |