Port 443: HTTP over TLS
Port 443 is the default port for the https URI scheme, where HTTP runs over TLS on TCP. HTTP/3 runs over QUIC on UDP. RFC 9114 lets servers offer HTTP/3 on any UDP port, and a client connecting directly to an https URI without an explicit port uses the scheme's default, 443. Windows SMB over QUIC also uses UDP 443 by default.
Updated
- Transport
- TCP / UDP
- Service
- HTTPS
- IANA service name
- https
- Range
- System port (0-1023)
- Related ports
- 80
Security Exposure
HTTPS is meant to be reachable, so the risk sits in the web application behind it and in the TLS configuration. TLS 1.0 and 1.1 are formally deprecated and lack support for current cryptographic algorithms. A server that still negotiates deprecated TLS versions or weak cipher suites weakens the protection HTTPS is supposed to provide.
Hardening
- Disable TLS 1.0 and 1.1, require TLS 1.2, and prefer TLS 1.3 where clients support it.
- Send an HTTP Strict-Transport-Security header so browsers interact with the site only over secure connections (RFC 6797).
- Keep management and admin interfaces off the public 443 listener, or put them behind a VPN or identity-aware proxy.
- Patch the web server, reverse proxy and application frameworks on a fixed schedule.
- Renew certificates automatically and monitor expiry dates.
Monitoring
Collect web server and reverse proxy access logs, and track negotiated TLS versions so legacy clients are visible before older versions are switched off. Alert on new listeners on 443 that are not in the asset inventory.
Frequently Asked Questions
Is port 443 TCP or UDP?→
Both. HTTPS over HTTP/1.1 and HTTP/2 uses TCP 443, and HTTP/3 runs over QUIC on UDP. RFC 9114 tells clients to fall back to TCP-based HTTP when UDP is blocked.
Which TLS versions should a server on port 443 accept?→
RFC 8996 deprecates TLS 1.0 and 1.1. RFC 9325 says implementations must support TLS 1.2, should support TLS 1.3, and must prefer TLS 1.3 when it is available.
What is the difference between port 80 and port 443?→
Port 80 carries plain HTTP. Port 443 is the default for https URIs, where HTTP runs inside TLS so traffic is encrypted and the server is authenticated by certificate.
Sources
- IANA Service Name and Port Number Registry: port 443
- RFC 9110: HTTP Semantics
- RFC 9114: HTTP/3
- RFC 8996: Deprecating TLS 1.0 and TLS 1.1
- RFC 9325: Recommendations for Secure Use of TLS and DTLS
- RFC 6797: HTTP Strict Transport Security (HSTS)
- Microsoft Learn: Secure SMB traffic in Windows Server
- MITRE ATT&CK T1110.001: Brute Force, Password Guessing
- Apache HTTP Server 2.4: Security Tips
- NVD: CVE-2021-41773
- RFC 8555: Automatic Certificate Management Environment (ACME)
Port assignments from the IANA Service Name and Transport Protocol Port Number Registry. Services can be configured to run on any port, so traffic on port 443 is not guaranteed to be HTTPS. Exploited-in-the-wild data from the CISA KEV catalog (CC0).