Tech

Explainer

Updated

What port does HTTP use?

Key facts

Port 80 is only the default: a URL can name any port, and RFC 9110 treats an address that spells out :80 as the same address with the port left off.

HTTP uses TCP port 80 by default. RFC 9110, the Internet Engineering Task Force standard that defines HTTP semantics, says that for an http URL, "If the port subcomponent is empty or not given, TCP port 80 (the reserved port for WWW services) is the default." The IANA port registry assigns port 80 to the service name http over TCP and UDP and cites RFC 9110 as its reference.

The default only applies when a URL leaves the port out. An address such as http://example.com:8080/ tells the browser to connect to port 8080 instead, because the http scheme identifies its server by a host and an optional port number.

What the port registry lists for HTTP

The IANA registry, last updated November 10, 2026, holds these entries for HTTP on ports 80, 443, 591 and 8008.

PortService name and transportRegistry description
80http (TCP, UDP)World Wide Web HTTP
80http (SCTP)HTTP
80www, www-http (TCP, UDP)World Wide Web HTTP
443https (TCP, UDP)http protocol over TLS/SSL
591http-alt (TCP, UDP)FileMaker, Inc. - HTTP Alternate (see Port 80)
8008http-alt (TCP, UDP)HTTP Alternate

The registry notes that the www and www-http entries duplicate the http service and should not be used for discovery purposes. The http entries over TCP and UDP name the IESG as assignee and RFC 9110 as the reference, while the http entry over SCTP cites RFC 9260 and the www-http entries name Tim Berners-Lee as assignee, all as listed in the registry.

HTTP and HTTPS ports compared

The secure scheme has its own default. RFC 9110 says that for an https URL with no port, "TCP port 443 (the reserved port for HTTP over TLS) is the default." It adds that resources under the https scheme have no shared identity with the http scheme and are distinct origins with separate namespaces, so http://example.com/ and https://example.com/ are two different sites as far as the protocol is concerned.

SchemeDefault portConnection
http80TCP
https443TCP secured with TLS

Both defaults are from RFC 9110, Sections 4.2.1 and 4.2.2.

Writing :80 in a URL changes nothing

Under the normalization rules of RFC 9110, when the port equals the default port for a scheme, the normal form is to omit it. The standard gives http://example.com:80/~smith/home.html and http://EXAMPLE.com/%7Esmith/home.html as equivalent addresses. The same section says that, outside an OPTIONS request, an empty path is equivalent to "/", and that the scheme and host are case-insensitive.

The port is also part of a site's identity. RFC 9110 defines the origin of a URL as the triple of scheme, host and port, and when the port is left out, the default for the scheme fills it in. That is why http://example.com/ and http://example.com:8080/ count as different origins, while http://example.com/ and http://example.com:80/ count as one.

Cases a reader meets next

  • CONNECT has no default port. For the CONNECT method used to open a tunnel through a proxy, RFC 9110 says "There is no default port; a client MUST send the port number even if the CONNECT request is based on a URI reference that contains an authority component with an elided port".
  • Networks may intercept port 80. RFC 9110 describes an interception proxy, also called a transparent proxy, which the client does not choose and which filters or redirects outgoing TCP port 80 packets. It says such proxies are commonly found on public network access points and within corporate firewalls.
  • The standard calls the authority of an http URL "a very weak sense of authority" because it depends on name resolution and on communication that might not be secured from an on-path attacker.
  • HTTP/3 runs over UDP. RFC 9110 says HTTP/3 uses QUIC as a secure multiplexed transport over UDP instead of TCP.

What changed and when

RFC 9110 was published in June 2022 on the Standards Track as STD 97. It obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615 and 7694, and portions of RFC 7230. Its port registration section says IANA updated the registry entries for ports 80 and 443 over UDP and TCP to use RFC 9110 as the reference and, where unspecified, to set the assignee to the IESG and the contact to the IETF Chair. The registry shows those http and https entries with a modification date of October 1, 2021, and the SCTP entries for both ports with a modification date of February 7, 2022.

For what a server sends back once a connection on port 80 is made, see what the HTTP 404 status code means and what the HTTP 301 status code means.

Have another question?