Service Name and Transport Protocol Port Number Registry (2024)

Last Updated
2024-04-30
Expert(s)
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, Jana Iyengar, and Michael ScharfSCTP: Michael TuexenDCCP: Eddie Kohler and Yoshifumi Nishida
Reference
[RFC6335]
Note
Service names and port numbers are used to distinguish between differentservices that run over transport protocols such as TCP, UDP, DCCP, andSCTP.Service names are assigned on a first-come, first-served process, asdocumented in [RFC6335].Port numbers are assigned in various ways, based on three ranges: SystemPorts (0-1023), User Ports (1024-49151), and the Dynamic and/or PrivatePorts (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 aredescribed in [RFC6335].Assigned ports both System and User ports SHOULD NOT be used withoutor prior to IANA registration.************************************************************************* PLEASE NOTE THE FOLLOWING: ** ** ASSIGNMENT OF A PORT NUMBER DOES NOT IN ANY WAY IMPLY AN ** ENDORsem*nT 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
Service Name and Transport Protocol Port Number Registry (1)
CSV
Service Name and Transport Protocol Port Number Registry (2)
XML
Service Name and Transport Protocol Port Number Registry (3)
HTML
Service Name and Transport Protocol Port Number Registry (4)
Plain text
Service Name Port Number Transport Protocol Description Assignee Contact Registration Date Modification Date Reference Service Code Unauthorized Use Reported Assignment Notes
vids-avtp 1853 tcp VIDS-AVTP [Sascha_Kuemmel] [Sascha_Kuemmel]
vids-avtp 1853 udp VIDS-AVTP [Sascha_Kuemmel] [Sascha_Kuemmel]
msnp 1863 tcp MSNP [William_Lai] [William_Lai]
msnp 1863 udp MSNP [William_Lai] [William_Lai]
paradym-31port 1864 tcp Paradym 31 Port [David_Wooden] [David_Wooden]
paradym-31port 1864 udp Paradym 31 Port [David_Wooden] [David_Wooden]
fjmpjps 1873 tcp Fjmpjps
fjmpjps 1873 udp Fjmpjps
mqtt 1883 tcp Message Queuing Telemetry Transport Protocol [OASIS] [Robin_Cover] 2015-02-10
mqtt 1883 udp Message Queuing Telemetry Transport Protocol [OASIS] [Robin_Cover] 2015-02-10
elad 1893 tcp ELAD Protocol [Franco_Milan] [Franco_Milan]
elad 1893 udp ELAD Protocol [Franco_Milan] [Franco_Milan]
linkname 1903 tcp Local Link Name Resolution [Dan_Harrington] [Dan_Harrington]
linkname 1903 udp Local Link Name Resolution [Dan_Harrington] [Dan_Harrington]
armadp 1913 tcp armadp [Kevin_Welton] [Kevin_Welton]
armadp 1913 udp armadp [Kevin_Welton] [Kevin_Welton]
spice 1923 tcp SPICE [Nicholas_Chua] [Nicholas_Chua]
spice 1923 udp SPICE [Nicholas_Chua] [Nicholas_Chua]
driveappserver 1930 tcp Drive AppServer [Andrew_Johnson] [Andrew_Johnson]
driveappserver 1930 udp Drive AppServer [Andrew_Johnson] [Andrew_Johnson]
amdsched 1931 tcp AMD SCHED [Michael_Walsh] [Michael_Walsh]
amdsched 1931 udp AMD SCHED [Michael_Walsh] [Michael_Walsh]
ctt-broker 1932 tcp CTT Broker [Jens_Edlund] [Jens_Edlund]
ctt-broker 1932 udp CTT Broker [Jens_Edlund] [Jens_Edlund]
xmapi 1933 tcp IBM LM MT Agent
xmapi 1933 udp IBM LM MT Agent
xaapi 1934 tcp IBM LM Appl Agent [Helga_Wolin] [Helga_Wolin]
xaapi 1934 udp IBM LM Appl Agent [Helga_Wolin] [Helga_Wolin]
macromedia-fcs 1935 tcp Macromedia Flash Communications Server MX [Pritham_Shetty] [Pritham_Shetty]
macromedia-fcs 1935 udp Macromedia Flash Communications server MX [Pritham_Shetty] [Pritham_Shetty]
jetcmeserver 1936 tcp JetCmeServer Server Port
jetcmeserver 1936 udp JetCmeServer Server Port
jwserver 1937 tcp JetVWay Server Port
jwserver 1937 udp JetVWay Server Port
jwclient 1938 tcp JetVWay Client Port
jwclient 1938 udp JetVWay Client Port
jvserver 1939 tcp JetVision Server Port
jvserver 1939 udp JetVision Server Port
beeyond-media 1943 tcp Beeyond Media [Bob_Deblier] [Bob_Deblier]
beeyond-media 1943 udp Beeyond Media [Bob_Deblier] [Bob_Deblier]
rapidbase 1953 tcp Rapid Base [Antoni_Wolski] [Antoni_Wolski]
rapidbase 1953 udp Rapid Base [Antoni_Wolski] [Antoni_Wolski]
webmachine 1963 tcp WebMachine [Tim_Jowers] [Tim_Jowers]
webmachine 1963 udp WebMachine [Tim_Jowers] [Tim_Jowers]
dlsrap 1973 tcp Data Link Switching Remote Access Protocol [Steve_T_Chiang] [Steve_T_Chiang]
dlsrap 1973 udp Data Link Switching Remote Access Protocol [Steve_T_Chiang] [Steve_T_Chiang]
lhtp 1983 tcp Loophole Test Protocol [Kade_Hansson] [Kade_Hansson]
lhtp 1983 udp Loophole Test Protocol [Kade_Hansson] [Kade_Hansson]
tr-rsrb-p3 1989 tcp cisco RSRB Priority 3 port
tr-rsrb-p3 1989 udp cisco RSRB Priority 3 port
stun-p3 1992 tcp cisco STUN Priority 3 port
stun-p3 1992 udp cisco STUN Priority 3 port
snmp-tcp-port 1993 tcp cisco SNMP TCP port
snmp-tcp-port 1993 udp cisco SNMP TCP port
brutus 2003 tcp Brutus Server [Johannes_Skov_Frands] [Johannes_Skov_Frands] 2008-02-28
brutus 2003 udp Brutus Server [Johannes_Skov_Frands] [Johannes_Skov_Frands] 2008-02-28
raid-am 2013 tcp
raid-cd 2013 udp
xinuexpansion3 2023 tcp
xinuexpansion3 2023 udp
device2 2030 tcp
device2 2030 udp
mobrien-chat 2031 tcp mobrien-chat [Mike_O_Brien] [Mike_O_Brien] 2004-11
mobrien-chat 2031 udp mobrien-chat [Mike_O_Brien] [Mike_O_Brien] 2004-11
blackboard 2032 tcp
blackboard 2032 udp
glogger 2033 tcp
glogger 2033 udp
scoremgr 2034 tcp
scoremgr 2034 udp
imsldoc 2035 tcp
imsldoc 2035 udp
e-dpnet 2036 tcp Ethernet WS DP network [Peter_Kaever] [Peter_Kaever] 2005-08
e-dpnet 2036 udp Ethernet WS DP network [Peter_Kaever] [Peter_Kaever] 2005-08
applus 2037 tcp APplus Application Server [Alfred_Weindl] [Marcus_Schairer] 2008-06-06 2021-07-20 Unauthorized Use Known on port 2037 Formerly was P2plus Application Server
applus 2037 udp APplus Application Server [Alfred_Weindl] [Marcus_Schairer] 2008-06-06 2021-07-20 Unauthorized Use Known on port 2037 Formerly was P2plus Application Server
objectmanager 2038 tcp
objectmanager 2038 udp
prizma 2039 tcp Prizma Monitoring Service [Dotan_Ofek] [Dotan_Ofek] 2005-12
prizma 2039 udp Prizma Monitoring Service [Dotan_Ofek] [Dotan_Ofek] 2005-12
isis-bcast 2043 tcp isis-bcast [Ken_Chapman] [Ken_Chapman]
isis-bcast 2043 udp isis-bcast [Ken_Chapman] [Ken_Chapman]
lot105-ds-upd 2053 tcp Lot105 DSuper Updates [Piers_Scannell] [Piers_Scannell]
lot105-ds-upd 2053 udp Lot105 DSuper Updates [Piers_Scannell] [Piers_Scannell]
icg-bridge 2063 tcp ICG Bridge Port
icg-bridge 2063 udp ICG Bridge Port
gxs-data-port 2073 tcp DataReel Database Socket [Douglas_M_Gaer] [Douglas_M_Gaer]
gxs-data-port 2073 udp DataReel Database Socket [Douglas_M_Gaer] [Douglas_M_Gaer]
radsec 2083 tcp Secure Radius Service [IESG] [IETF_Chair] 2005-05 [RFC6614] The TCP port 2083 was already previously assigned by IANA for "RadSec", an early implementation of RADIUS/TLS, prior to issuance of this RFC. This early implementation can be configured to be compatible to RADIUS/TLS as specified by the IETF. See [RFC6614], Appendix A for details.
radsec 2083 udp Secure Radius Service [IESG] [IETF_Chair] 2005-05 2014-07-14 [RFC7360] The UDP port 2083 was already previously assigned by IANA for "RadSec", an early implementation of RADIUS/TLS, prior to issuance of this RFC.
descent3 2092 tcp Descent 3 [Kevin_Bentley] [Kevin_Bentley]
descent3 2092 udp Descent 3 [Kevin_Bentley] [Kevin_Bentley]
nbx-cc 2093 tcp NBX CC
nbx-cc 2093 udp NBX CC
zephyr-clt 2103 tcp Zephyr serv-hm connection
zephyr-clt 2103 udp Zephyr serv-hm connection
hsl-storm 2113 tcp HSL StoRM [Jost_fa*ganel] [Jost_fa*ganel]
hsl-storm 2113 udp HSL StoRM [Jost_fa*ganel] [Jost_fa*ganel]
gtp-control 2123 tcp GTP-Control Plane (3GPP) [Alessio_Casati] [Alessio_Casati]
gtp-control 2123 udp GTP-Control Plane (3GPP) [Alessio_Casati] [Alessio_Casati]
xds 2130 tcp XDS [Peter_Zurich] [Peter_Zurich]
ID Name Organization Contact URI Last Updated
[Alessio_Casati] Alessio Casati
[Alfred_Weindl] Alfred Weindl 2021-08-09
[Andrew_Johnson] Andrew Johnson
[Antoni_Wolski] Antoni Wolski
[Bob_Deblier] Bob Deblier
[Dan_Harrington] Dan Harrington
[David_Wooden] David Wooden
[Dotan_Ofek] Dotan Ofek 2005-12
[Douglas_M_Gaer] Douglas M. Gaer
[Franco_Milan] Franco Milan
[Helga_Wolin] Helga Wolin
[IESG] IESG
[IETF_Chair] IETF Chair IETF
[Jens_Edlund] Jens Edlund 2005-08
[Johannes_Skov_Frands] Johannes Skov Frandsen 2008-02-28
[Jost_fa*ganel] Jost fa*ganel
[Kade_Hansson] Kade Hansson
[Ken_Chapman] Ken Chapman
[Kevin_Bentley] Kevin Bentley
[Kevin_Welton] Kevin Welton
[Marcus_Schairer] Marcus Schairer 2021-08-09
[Michael_Walsh] Michael Walsh
[Mike_O_Brien] Mike O'Brien 2004-11
[Nicholas_Chua] Nicholas Chua
[OASIS] OASIS 2015-02-10
[Peter_Kaever] Peter Kaever 2005-08
[Peter_Zurich] Peter Zurich
[Piers_Scannell] Piers Scannell
[Pritham_Shetty] Pritham Shetty
[Robin_Cover] Robin Cover OASIS KMIP Technical Committee 2011-07-25
[Sascha_Kuemmel] Sascha Kuemmel
[Steve_T_Chiang] Steve T. Chiang
[Tim_Jowers] Tim Jowers
[William_Lai] William Lai
Service Name and Transport Protocol Port Number Registry (2024)

FAQs

What are the registered ports for TCP? ›

TCP/IP Ports

Registered ports are from 1024 to 49151. The remainder of the ports from 49152 to 65535 can be used dynamically by applications.

How to check service name from port number? ›

To list what services are listening* on a particular port on a device in your environment, run the following commands in a Windows Command Line or a Linux Terminal window on the device the port is on: Windows: netstat -ano | findstr [Port Number] Linux: netstat -ano | grep [Port Number]

How to register a port with IANA? ›

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].

What is the port number and service name? ›

The most 50 significant ports are listed here:
Port NumberService nameTransport protocol
25SMTPTCP
53DNSTCP, UDP
69TFTPUDP
80HTTPTCP, UDP, SCTP
54 more rows
Apr 15, 2024

What is a registered port? ›

A registered port is a network port designated for use with a certain protocol or application. Ports with numbers 0–1023 are called system or well-known ports; ports with numbers 1024-49151 are called user or registered ports, and ports with numbers 49152-65535 are called dynamic, private or ephemeral ports.

Is 8080 a registered port? ›

Port number 8080 is usually used for web servers. When a port number is added to the end of the domain name, it drives traffic to the web server. However, users can not reserve port 8080 for secondary web servers.

How do I check all ports on my network? ›

If you would like to test ports on your computer, use the Windows command prompt and the CMD command netstat -ano. Windows will show you all currently existing network connections via open ports or open, listening ports that are currently not establishing a connection.

How do I identify a port? ›

How do I find my IP address and port? You find your IP address and ports by opening the console, entering the “netstat -a” command, and then looking for the numbers under Local Address.

How do I know if a port number is used? ›

Use the netstat -anp | find "port number" command to find whether a port is occupied by an another process or not.

How do I add a port number to my server? ›

Click Start > All Programs > Administrative Tools > Windows Firewall with Advanced Security.
  1. Select Inbound Rules.
  2. Select Action > New Rule.
  3. Proceed with the New Inbound Rule Wizard and enter the following information: Rule Type = Port. Protocol and Ports = TCP. Specific port = 8031. Action = Allow the connection.

What are the three types of port numbers? ›

The port numbers are divided into three ranges: the well-known ports, the registered ports, and the dynamic or private ports.

What is the difference between port number and protocol number? ›

You can call the number (IP address) to talk to the computer, then dial the extension (port) to talk to a specific application. An application needs to be listening on a port in order to communicate. A protocol is just the language that the two applications on either end of a conversation agree to speak in.

What is the difference between protocol and port? ›

A protocol is a specification for how two devices should exchange data in a way that they can both understand. A port is kind of a numbered 'tag' that helps a computer decide who should receive an incoming piece of data.

What are the two types of port numbers? ›

The port numbers are divided into three ranges:
  • Well-known ports. The well known ports are those from 0 - 1,023. ...
  • Registered ports. The registered ports are those from 1,024 - 49,151. ...
  • Dynamic and/or private ports. The dynamic and/or private ports are those from 49,152 - 65,535.

What ports are 49152 to 65535? ›

Dynamic ports—Ports in the range 49152 to 65535 are not assigned, controlled, or registered. They are used for temporary or private ports. They are also known as private or non-reserved ports. Clients should choose ephemeral port numbers from this range, but many systems do not.

What are TCP ports 80 and 443 typically used by? ›

All web traffic, either encrypted or unencrypted, is handled via Port. Generally, port 80 is used for HTTP, and Port 443 is used for HTTPS protocol. This article will discuss about the difference between Port 80 (HTTP) and Port 443 (HTTPS) and the steps to enable them on different operating systems.

What are 135 TCP ports? ›

Port 135 on your computer is used by a service called "DCOM Service Control Manager" from Microsoft. This port lets other devices know where to find DCOM services on your computer. However, it can be risky if exposed to the internet.

Is port 443 TCP or UDP? ›

UDP port 53 is used for DNS, TCP port 80 is used for non-encrypted web services, and TCP port 443 is used for encrypted web services.

Top Articles
Latest Posts
Article information

Author: Rev. Porsche Oberbrunner

Last Updated:

Views: 6418

Rating: 4.2 / 5 (73 voted)

Reviews: 80% of readers found this page helpful

Author information

Name: Rev. Porsche Oberbrunner

Birthday: 1994-06-25

Address: Suite 153 582 Lubowitz Walks, Port Alfredoborough, IN 72879-2838

Phone: +128413562823324

Job: IT Strategist

Hobby: Video gaming, Basketball, Web surfing, Book restoration, Jogging, Shooting, Fishing

Introduction: My name is Rev. Porsche Oberbrunner, I am a zany, graceful, talented, witty, determined, shiny, enchanting person who loves writing and wants to share my knowledge and understanding with you.