Tech

Explainer

Updated

What port does HTTPS use?

Key facts

IANA registers port 443 for the https service on TCP, UDP and SCTP, and HTTP/3 reaches servers over QUIC, which runs on UDP.

HTTPS uses port 443 by default. RFC 9110, Section 4.2.2, the current HTTP standard, defines the https scheme and says: "If the port subcomponent is empty or not given, TCP port 443 (the reserved port for HTTP over TLS) is the default." So a browser that opens an address such as https://example.com/ with no port written in it connects to port 443 on that host.

What the port registry lists

The IANA Service Name and Transport Protocol Port Number Registry, last updated 2026-11-10, holds three entries for the https service on port 443.

TransportRegistry descriptionReference
TCPhttp protocol over TLS/SSLRFC 9110
UDPhttp protocol over TLS/SSLRFC 9110
SCTPHTTPSRFC 9260

The TCP and UDP entries name the IESG as assignee and the IETF Chair as contact, with a modification date of 2021-10-01, according to the IANA registry. The SCTP entry carries a modification date of 2022-02-07. The same registry page places port 443 in the System Ports range of 0 to 1023, which is assigned through the IETF Review or IESG Approval procedures, while ports 49152 to 65535 are dynamic or private and are not assigned.

RFC 9110, Section 18.9 records that IANA updated the registry for the services on ports 80 and 443 that use UDP or TCP so that they use RFC 9110 as the reference, with the IESG as assignee and the IETF Chair as contact where none was set.

Where HTTP/3 fits

HTTP/3 carries HTTP over QUIC, and RFC 9114 describes how a client may reach a resource at an https URI by opening a QUIC connection to the host on the port the URI indicates. The references of RFC 9114 list QUIC itself, RFC 9000, as a UDP based multiplexed and secure transport.

RFC 9114 adds two rules a reader meets in practice. Servers may serve HTTP/3 on any UDP port, and an alternative service advertisement always includes an explicit port; its own example, the header Alt-Svc: h3=":50781", tells the client HTTP/3 is available on UDP port 50781 at the same host, as set out in Section 3.1.1. When a QUIC connection cannot be set up, for example because UDP is blocked, clients should fall back to the TCP based versions of HTTP, under Section 3.1.

HTTPS and HTTP side by side

Questionhttpshttp
Default portTCP 443TCP 80
Defined inRFC 9110, Section 4.2.2RFC 9110, Section 4.2.1
ConnectionTLS securedTCP

Both defaults come from RFC 9110, which names TCP port 80 as the reserved port for WWW services and the default for the http scheme. The same document says resources served under https have no shared identity with the http scheme: they are distinct origins with separate namespaces,, per Section 4.2.2.

Cases a reader meets next

  • A port written in the address. The default applies only when the URI leaves the port out. An address such as https://example.com:8000/ names its own port, and RFC 9110 gives an example of one host running distinct services on ports 443 and 8000, in Section 4.3.3.
  • Writing :443 by hand. RFC 9110, Section 4.3.1 gives the origin of https://Example.Com/happy.js as https, example.com and 443, which it also writes as https://example.com:443. Under its normalization rules in Section 4.2.3, when the port equals the default port for a scheme, the normal form leaves the port out.
  • Traffic on 443 is not proof of HTTPS. The IANA registry notes that assigning a port does not endorse an application, and that traffic flowing to or from a registered port does not necessarily correspond to the assigned service.

What changed and when

  • May 2000. RFC 2818, HTTP Over TLS, an Informational memo, said that when HTTP/TLS runs over a TCP/IP connection the default port is 443, and that common practice had been to run HTTP/TLS on a separate port to tell the protocols apart.
  • October 2021. The IANA entries for https on port 443 over TCP and UDP carry a modification date of 2021-10-01 and cite RFC 9110, per the registry.
  • February 2022. The SCTP entry for https on port 443 carries a modification date of 2022-02-07 and cites RFC 9260, per the same registry.
  • June 2022. RFC 9110, a Standards Track document, obsoleted RFC 2818 among others and now defines the https scheme with TCP port 443 as its default; its appendix lists no changes from RFC 2818. The same month, RFC 9114 set out HTTP/3 over QUIC on the Standards Track.

For what the server says back once a connection is open, see what the HTTP 301 status code means and what the HTTP 400 status code means.

Have another question?