HTTPS Port Number: Port 443 Explained

HTTPS uses port 443 by default. That is the port number assigned by IANA, the organisation that manages internet addressing standards worldwide. Every browser assumes port 443 when you load a secure website, even though you never type it into the address bar.

Port numbers work like numbered channels on a server. Each one handles a specific type of traffic. Port 443 is the channel reserved for encrypted web traffic, protected by TLS or SSL.

Default Port: What Port Number Does HTTPS Use?

The HTTPS port number is 443. IANA assigned port 443 to HTTPS under RFC 2818, and every browser treats it as the default for any URL beginning with "https://".

You never type it manually. When you visit https://example.com, your browser connects to port 443 on that server automatically. If HTTPS were running on a non-standard port, the URL would include it explicitly, for example: https://example.com:8443.

• HTTPS = HyperText Transfer Protocol Secure (the encrypted version of HTTP)
• Port 443 = the default TCP port assigned to HTTPS traffic by IANA
• TLS/SSL = the encryption protocol that secures all data passing through port 443

HTTP vs HTTPS: What Is the Difference Between Port 80 and Port 443?

HTTP uses port 80. HTTPS uses port 443. Port 443 carries encrypted traffic. Port 80 does not.

When you connect through port 80, any data in transit (passwords, form submissions, personal details) can be intercepted by a third party. Port 443 encrypts everything using TLS (Transport Layer Security), making intercepted data unreadable even if it is captured.

Quick reference:

• Port 80 = HTTP, unencrypted, standard web traffic
• Port 443 = HTTPS, encrypted, secure web traffic
• TLS = the encryption layer that makes port 443 secure

HTTP vs HTTPS: Key Differences

Alternative Ports: Can HTTPS Use a Port Other Than 443?

Yes. HTTPS can run on any TCP port, not just 443. Port 443 is the default, but web servers can be configured to serve HTTPS traffic on any available port number.

In practice, most administrators stick with 443 because browsers connect to it automatically. Using a non-standard port means users must type it into the URL manually (for example, https://example.com:8443), which creates friction and can trigger blocks on corporate firewalls. Most enterprise network switches and routers are preconfigured to pass port 443 traffic by default.

What Is Port 8443?

Port 8443 is the standard alternative to port 443 for HTTPS traffic. It is the default HTTPS port for Apache Tomcat, used because binding to ports below 1024 requires root-level system privileges on Linux servers. Port 8443 uses the same TLS encryption as port 443 and offers identical security.

What Is Port 2053?

Port 2053 is an alternative HTTPS port used within Cloudflare's network infrastructure. It allows HTTPS traffic to be proxied through Cloudflare on a non-standard port, typically used when port 443 is restricted or unavailable on a given network.

What Is Port 2083?

Port 2083 is the default HTTPS port for cPanel, the web hosting control panel used by the majority of shared hosting providers. It allows secure, encrypted access to hosting dashboards without conflicting with the site's primary port 443 traffic.

What Is Port 2096?

Port 2096 is the secure HTTPS port for webmail access on cPanel-based servers. It provides an encrypted connection to web-based email clients (such as Roundcube or Horde) hosted on the same server as the main website.

Port 443 History: Why Was 443 Chosen for HTTPS?

Port 443 was assigned to HTTPS by IANA (Internet Assigned Numbers Authority), the global body responsible for managing internet port numbers. The assignment was formalised in RFC 2818, published in May 2000.

There was no technical reason 443 was chosen over any other available number. IANA maintains a registry of well-known ports: numbers 0 to 1023 reserved for established internet protocols. When HTTPS was standardised, 443 was an available number in that reserved range, allocated to ensure consistent recognition across all browsers, servers, and network devices.

• Port numbers 0 to 1023 are well-known ports, reserved and managed by IANA
• Port 80 was already assigned to HTTP; 443 was the next logical allocation for its secure counterpart
• RFC 2818 (2000) formalised port 443 as the HTTPS default
• Every browser, firewall, and web server recognises port 443 by default as a result of this standardisation

Frequently Answered Questions

Does HTTPS Always Use Port 443?

HTTPS uses port 443 by default, but it is not a technical requirement. Any web server can be configured to serve HTTPS traffic on an alternative port. When a non-standard port is used, it must be included explicitly in the URL, for example https://example.com:8443.

Is Port 443 Always Encrypted?

Yes. All traffic through port 443 is encrypted using TLS. However, the strength of that encryption depends on the TLS version and the validity of the certificate in use. An expired or misconfigured certificate will still attempt to use port 443, but browsers will block access and display a security warning.

Can I Change the HTTPS Port on My Web Server?

Yes. In Apache, update the Listen directive and the VirtualHost block in your configuration file. In Nginx, update the listen directive in the server block. After changing the port, update your firewall rules to allow traffic on the new port. Otherwise, connections will be blocked before they reach the server.

What Happens if Port 443 Is Blocked by a Firewall?

HTTPS connections will fail and users will receive a connection error. Port 443 is blocked in some corporate and restricted network environments as a security control. In these cases, administrators may configure HTTPS on an alternative port such as 8443, or work with the network team to whitelist port 443 for specific domains.

Is There a Difference Between an SSL Port and an HTTPS Port?

Not in practice. "SSL port" is an informal term that most commonly refers to port 443. SSL (Secure Sockets Layer) is the older predecessor to TLS, which is the current encryption standard. The term persists in everyday use even though modern HTTPS connections use TLS, not SSL.