Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2024-04-30
- 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
sunrpc | 111 | tcp | SUN Remote Procedure Call | [Chuck_McManis] | [Chuck_McManis] | ||||||
sunrpc | 111 | udp | SUN Remote Procedure Call | [Chuck_McManis] | [Chuck_McManis] | ||||||
erpc | 121 | tcp | Encore Expedited Remote Pro.Call | [Jack_ONeil] | [Jack_ONeil] | ||||||
erpc | 121 | udp | Encore Expedited Remote Pro.Call | [Jack_ONeil] | [Jack_ONeil] | ||||||
rpc2portmap | 369 | tcp | rpc2portmap | ||||||||
rpc2portmap | 369 | udp | rpc2portmap | ||||||||
courier | 530 | tcp | rpc | ||||||||
courier | 530 | udp | rpc | ||||||||
banyan-rpc | 567 | tcp | banyan-rpc | [Tom_Lemaire] | [Tom_Lemaire] | ||||||
banyan-rpc | 567 | udp | banyan-rpc | [Tom_Lemaire] | [Tom_Lemaire] | ||||||
http-rpc-epmap | 593 | tcp | HTTP RPC Ep Map | [Edward_Reus] | [Edward_Reus] | ||||||
http-rpc-epmap | 593 | udp | HTTP RPC Ep Map | [Edward_Reus] | [Edward_Reus] | ||||||
xmlrpc-beep | 602 | tcp | XML-RPC over BEEP | [RFC3529] | |||||||
xmlrpc-beep | 602 | udp | XML-RPC over BEEP | [RFC3529] | |||||||
mxxrlogin | 1035 | tcp | MX-XR RPC | [Valassis] | [John_Eckert] | 2003-04 | 2015-05-05 | ||||
mxxrlogin | 1035 | udp | MX-XR RPC | [Valassis] | [John_Eckert] | 2003-04 | 2015-05-05 | ||||
pammrpc | 1633 | tcp | PAMMRPC | [John_Britton] | [John_Britton] | ||||||
pammrpc | 1633 | udp | PAMMRPC | [John_Britton] | [John_Britton] | ||||||
hydra | 2374 | tcp | Hydra RPC | [Jacob_Feisley] | [Jacob_Feisley] | 2009-01-21 | |||||
swarm | 2377 | tcp | RPC interface for Docker Swarm | [Docker_Inc] | [Mike_Goelzer] | 2016-12-23 | |||||
aic-oncrpc | 2786 | tcp | aic-oncrpc - Destiny MCD database | [Brad_Parker] | [Brad_Parker] | ||||||
aic-oncrpc | 2786 | udp | aic-oncrpc - Destiny MCD database | [Brad_Parker] | [Brad_Parker] | ||||||
phoenix-rpc | 3347 | tcp | Phoenix RPC | [Ian_Anderson] | [Ian_Anderson] | ||||||
phoenix-rpc | 3347 | udp | Phoenix RPC | [Ian_Anderson] | [Ian_Anderson] | ||||||
3comfaxrpc | 3446 | tcp | 3Com FAX RPC port | [Christopher_Wells_2] | [Christopher_Wells_2] | 2002-04 | |||||
3comfaxrpc | 3446 | udp | 3Com FAX RPC port | [Christopher_Wells_2] | [Christopher_Wells_2] | 2002-04 | |||||
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 | |||||
xrpc-registry | 3651 | tcp | XRPC Registry | [Slava_Monich] | [Slava_Monich] | 2003-01 | |||||
xrpc-registry | 3651 | udp | XRPC Registry | [Slava_Monich] | [Slava_Monich] | 2003-01 | |||||
adrep | 3954 | tcp | AD Replication RPC | [Robert_Ball] | [Robert_Ball] | 2008-03-26 | |||||
adrep | 3954 | udp | AD Replication RPC | [Robert_Ball] | [Robert_Ball] | 2008-03-26 | |||||
converge | 4774 | tcp | Converge RPC | [Asteris_LLC] | [Steven_Borrelli] | 2016-09-16 | |||||
csrpc | 5063 | tcp | centrify secure RPC | [Paul_Moore] | [Paul_Moore] | 2009-10-28 | |||||
apsolab-rpc | 5474 | udp | The Apsolab company's status query protocol | [Apsolab_Inc] | [Jean-Francois_Gauthier] | 2014-11-10 | |||||
vts-rpc | 5780 | tcp | Visual Tag System RPC | [Graham_Bloice] | [Graham_Bloice] | 2009-09-17 | |||||
elipse-rec | 6515 | tcp | Elipse RPC Protocol | [F_Englert] | [F_Englert] | 2007-09-17 | |||||
elipse-rec | 6515 | udp | Elipse RPC Protocol | [F_Englert] | [F_Englert] | 2007-09-17 | |||||
purityrpc | 8117 | tcp | Purity replication clustering and remote management | [Pure_Storage] | [Steve_Hodgson] | 2013-08-13 | |||||
semi-grpc | 8710 | tcp | gRPC for SEMI Standards implementations | [SEMI] | [Albert_Fuchigami] | 2020-01-10 | |||||
golem | 9005 | tcp | Golem Inter-System RPC | [Jose_Luis_Tallon] | [Jose_Luis_Tallon] | 2015-03-09 | |||||
glrpc | 9080 | tcp | Groove GLRPC | [Adrian_Popescu] | [Adrian_Popescu] | 2002-09 | |||||
glrpc | 9080 | udp | Groove GLRPC | [Adrian_Popescu] | [Adrian_Popescu] | 2002-09 | |||||
gnmi-gnoi | 9339 | tcp | gRPC Network Mgmt/Operations Interface | [Google_Netops] | [gNxi_Maintainers] | 2019-05-09 | |||||
gribi | 9340 | tcp | gRPC Routing Information Base Interface | [Google_Networking] | [Rob_Shakir] | 2022-03-29 | |||||
p4runtime | 9559 | tcp | P4Runtime gRPC Service | [Open_Networking_Foundation] | [Antonin_Bas] | 2020-09-22 | |||||
a-trust-rpc | 13832 | tcp | Certificate Management and Issuing | [A-Trust_GmbH] | [Patrick_Hagelkruys] | 2023-06-05 | |||||
filenet-rpc | 32769 | tcp | Filenet RPC | [Daniel_Whelan] | [Daniel_Whelan] | ||||||
filenet-rpc | 32769 | udp | Filenet RPC | [Daniel_Whelan] | [Daniel_Whelan] | ||||||
caerpc | 42510 | tcp | CA eTrust RPC | [Jon_Press] | [Jon_Press] | 2005-08 | |||||
caerpc | 42510 | udp | CA eTrust RPC | [Jon_Press] | [Jon_Press] | 2005-08 | |||||
sun-rpc | SUN Remote Procedure Call | ||||||||||
bridgeprotocol | tcp | JSON RPC Bridge Protocol | [Michel_Stam_2] | [Michel_Stam_2] | 2012-11-20 | Defined TXT keys: path, version | |||||
stingray-rpc | tcp | Stingray Remote Procedure Call | [IK_SATPROF_LLC] | [Sergey_Zubov_2] | 2014-05-02 | Defined TXT keys: None | |||||
tivo-mindrpc | tcp | TiVo RPC Protocol | [TiVo_Inc] | [Developer_Support_2] | 2011-10-18 | Defined TXT keys: None | |||||
tzrpc | tcp | TZ-Software remote procedure call based synchronization protocol | [Thomas_Zwick] | [Thomas_Zwick] | 2011-10-12 | Defined TXT keys: Proprietary |