# What port does HTTP use?

> HTTP uses TCP port 80 by default. RFC 9110 makes port 80 the default for http URLs, and IANA assigns port 80 to the http service.

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

- Type: Explainer
- Section: Tech
- By: Tech Desk
- Published: 2026-11-13T05:46:52-05:00
- Updated: 2026-11-13T05:46:52-05:00
- Checked: 2026-11-13T05:45:11-05:00
- URL: https://factsdesk.com/tech/what-port-does-http-use/

## Key facts

- HTTP uses TCP port 80 by default: RFC 9110 says that when an http URL gives no port, TCP port 80, the reserved port for WWW services, is the default. Source: [RFC Editor (Internet Engineering Task Force)](https://www.rfc-editor.org/rfc/rfc9110.html). Confirmed 2026-11-13T05:45:11-05:00. Cite: https://factsdesk.com/tech/what-port-does-http-use/#http-uses-tcp-port-80-by-default-rfc-9110-says-that-when-an
- The IANA port registry assigns port 80 to the service name http over both TCP and UDP, with the IESG as assignee and RFC 9110 as the reference. Source: [Internet Assigned Numbers Authority (IANA)](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=http). Confirmed 2026-11-13T05:45:11-05:00. Cite: https://factsdesk.com/tech/what-port-does-http-use/#the-iana-port-registry-assigns-port-80-to-the-service-name
- The https scheme defaults to TCP port 443, the reserved port for HTTP over TLS, and RFC 9110 says http and https resources are distinct origins. Source: [RFC Editor (Internet Engineering Task Force)](https://www.rfc-editor.org/rfc/rfc9110.html). Confirmed 2026-11-13T05:45:11-05:00. Cite: https://factsdesk.com/tech/what-port-does-http-use/#the-https-scheme-defaults-to-tcp-port-443-the-reserved-port
- RFC 9110 says the normal form of an http URL omits a port equal to the default, and gives http://example.com:80/~smith/home.html as equivalent to http://EXAMPLE.com/%7Esmith/home.html. Source: [RFC Editor (Internet Engineering Task Force)](https://www.rfc-editor.org/rfc/rfc9110.html). Confirmed 2026-11-13T05:45:11-05:00. Cite: https://factsdesk.com/tech/what-port-does-http-use/#rfc-9110-says-the-normal-form-of-an-http-url-omits-a-port
- IANA lists port 8080 over TCP as http-alt, described as HTTP Alternate (see port 80), and port 8008 as a second http-alt entry. Source: [Internet Assigned Numbers Authority (IANA)](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=http). Confirmed 2026-11-13T05:45:11-05:00. Cite: https://factsdesk.com/tech/what-port-does-http-use/#iana-lists-port-8080-over-tcp-as-http-alt-described-as-http

HTTP uses TCP port 80 by default. [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-http-uri-scheme), 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](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=http) 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](https://www.rfc-editor.org/rfc/rfc9110.html#name-http-uri-scheme) identifies its server by a host and an optional port number.

## What the port registry lists for HTTP

The [IANA registry](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=http), last updated November 10, 2026, holds these entries for HTTP on ports 80, 443, 591 and 8008.

| Port | Service name and transport | Registry description |
| --- | --- | --- |
| 80 | http (TCP, UDP) | World Wide Web HTTP |
| 80 | http (SCTP) | HTTP |
| 80 | www, www-http (TCP, UDP) | World Wide Web HTTP |
| 443 | https (TCP, UDP) | http protocol over TLS/SSL |
| 591 | http-alt (TCP, UDP) | FileMaker, Inc. - HTTP Alternate (see Port 80) |
| 8008 | http-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](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=http).

## HTTP and HTTPS ports compared

The secure scheme has its own default. [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-https-uri-scheme) 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.

| Scheme | Default port | Connection |
| --- | --- | --- |
| http | 80 | TCP |
| https | 443 | TCP secured with TLS |

Both defaults are from [RFC 9110, Sections 4.2.1 and 4.2.2](https://www.rfc-editor.org/rfc/rfc9110.html#name-https-uri-scheme).

## Writing :80 in a URL changes nothing

Under the [normalization rules of RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-https-normalization-and-com), 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](https://www.rfc-editor.org/rfc/rfc9110.html#name-uri-origin) 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](https://www.rfc-editor.org/rfc/rfc9110.html#name-connect) 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](https://www.rfc-editor.org/rfc/rfc9110.html#name-intermediaries) 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](https://www.rfc-editor.org/rfc/rfc9110.html#name-http-origins) 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](https://www.rfc-editor.org/rfc/rfc9110.html#name-history-and-evolution) says HTTP/3 uses QUIC as a secure multiplexed transport over UDP instead of TCP.

## What changed and when

[RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html) 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](https://www.rfc-editor.org/rfc/rfc9110.html#name-port-registration) 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](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=http) 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](/tech/what-does-the-http-404-status-code-mean/) and [what the HTTP 301 status code means](/tech/what-does-the-http-301-status-code-mean/).

## Sources

1. [RFC 9110: HTTP Semantics](https://www.rfc-editor.org/rfc/rfc9110.html), RFC Editor (Internet Engineering Task Force), 2022-06 (primary source)
2. [Service Name and Transport Protocol Port Number Registry](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=http), Internet Assigned Numbers Authority (IANA), 2026-11-10 (primary source)

## Asked next

- [What does the HTTP 301 status code mean?](https://factsdesk.com/tech/what-does-the-http-301-status-code-mean/): HTTP 301 means Moved Permanently: the resource has a new permanent URI, and future references to it ought to use the new address, under RFC 9110.
- [What does the HTTP 404 status code mean?](https://factsdesk.com/tech/what-does-the-http-404-status-code-mean/): HTTP 404 Not Found means the server did not find a current representation for the target resource or is not willing to disclose that one exists.
- [What port does SSH use?](https://factsdesk.com/tech/what-port-does-ssh-use/): SSH uses port 22. IANA assigns port 22 to the Secure Shell (SSH) Protocol, and RFC 4253 says an SSH server normally listens for TCP connections there.
- [What port does HTTPS use?](https://factsdesk.com/tech/what-port-does-https-use/): HTTPS uses TCP port 443 by default: under RFC 9110, an https address with no port named goes to port 443, the reserved port for HTTP over TLS.
- [Trump names Pentagon CIO Kirsten Davies to lead national cyber office](https://factsdesk.com/tech/who-is-the-new-national-cyber-director/): President Trump named Kirsten A. Davies, the Pentagon's chief information officer, on Nov. 19, 2026 to lead the national cyber director office.
- [CrowdStrike says a Windows content update caused its July 2024 outage](https://factsdesk.com/tech/what-caused-the-crowdstrike-outage/): CrowdStrike's root cause analysis says a content update for its Windows sensor, released July 19, 2024, caused the widespread outage.
