Top Qs
Timeline
Chat
Perspective

List of TCP and UDP port numbers

From Wikipedia, the free encyclopedia

Remove ads
Remove ads

This is a list of TCP and UDP port numbers used by protocols for operation of network applications. The Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP) only need one port for bidirectional traffic. TCP usually uses port numbers that match the services of the corresponding UDP implementations, if they exist, and vice versa.

The Internet Assigned Numbers Authority (IANA) is responsible for maintaining the official assignments of port numbers for specific uses,[1] However, many unofficial uses of both well-known and registered port numbers occur in practice. Similarly, many of the official assignments refer to protocols that were never or are no longer in common use. This article lists port numbers and their associated protocols that have experienced significant uptake.

Remove ads

Table legend

More information Cell, Description ...
Remove ads

Well-known ports

Summarize
Perspective

The port numbers in the range from 0 to 1023 (0 to 210 − 1) are the well-known ports or system ports.[3] They are used by system processes that provide widely used types of network services. On Unix-like operating systems, a process must execute with superuser privileges to be able to bind a network socket to an IP address using one of the well-known ports.[5]

More information Port, TCP ...
Remove ads

Registered ports

Summarize
Perspective

The range of port numbers from 1024 to 49151 (210 to 215 + 214 − 1) are the registered ports. They are assigned by IANA for specific service upon application by a requesting entity.[2] On most systems, registered ports can be used without superuser privileges.

More information Port, TCP ...
Remove ads

Dynamic, private or ephemeral ports

Summarize
Perspective

The range 49152–65535 (215 + 214 to 216 − 1), 16 384 ports, contains dynamic or private ports that cannot be registered with IANA.[486] This range is used for private or customized services, for temporary purposes, and for automatic allocation of ephemeral ports.

More information Port, TCP ...
Remove ads

Note

  1. TCP port 465 was originally assigned to allow the use of SMTP over SSL (SMTPS), but practical concerns meant that it was left unused and according to the registration rules at that time was subsequently revoked and eventually re-assigned for use by Cisco's URD protocol. Subsequently, port 587 was assigned as the SMTP submission port, but was initially in plaintext, with encryption eventually provided years later by the STARTTLS extension. At the same time, the subsequent adoption of the usage of 465 as an SSL-enabled SMTP submission port, even though the original registration did not envision that usage and despite the fact that it was registered to another service has endured. Subsequently, RFC 8314, in a special exemption to the normal assignment process as defined by RFC 6335, acknowledges the de-facto situation and not only designates message submission over implicit TLS as an 'alternate usage assignment' but establishes this as the preferred method and calls for transition away from port 587 and STARTTLS.
  2. Deployment typically occurs only directly over UDP, but other underlying protocol layers which meet the requirements described in the specification are possible.
Remove ads

See also

[212]

References and notes

Loading content...

Further reading

Loading content...
Loading related searches...

Wikiwand - on

Seamless Wikipedia browsing. On steroids.

Remove ads