Port 443/tcp: HTTPS (HTTP over TLS/SSL)
Category: Web & Application. Range: well-known. Status: iana registered.
What runs here
HTTPS wraps HTTP inside a TLS session, so the TCP handshake is followed by a TLS handshake (certificate exchange, cipher negotiation) before any HTTP request or response is exchanged. Port 443/tcp is IANA's registered default and is referenced from RFC 9110 as the default port for the https URI scheme. It now carries the overwhelming majority of web traffic, including HTTP/2 and, via QUIC over UDP on the same port number, HTTP/3.
Why it matters
Because the payload is encrypted, an analyst usually cannot read the request or response directly, so attention shifts to metadata: the TLS handshake (SNI hostname, JA3/JA3S fingerprint, certificate subject/issuer, freshly-issued or self-signed certs), connection timing and volume, and destination IP/ASN reputation. Because 443 is essentially never blocked outbound, it is the single most common port for malware C2 and exfiltration to hide in, so being on 443 is not by itself evidence of legitimacy.
Where you see it
Legitimately: essentially all modern web browsing, API calls, software updates, cloud service traffic. Anomalously/maliciously: C2 frameworks using HTTPS to blend with normal traffic, domain fronting or fronted-CDN abuse, self-signed or very recently issued certificates on a beaconing destination, or JA3 fingerprints matching known offensive tooling rather than a standard browser.
What to look for
| Signal | What it means |
|---|---|
| TLS SNI and JA3/JA3S fingerprint | The Server Name Indication field is visible even in encrypted traffic and identifies the intended hostname; JA3/JA3S fingerprints can flag TLS stacks belonging to known malware/C2 frameworks rather than a real browser. |
| Certificate metadata | Subject, issuer, validity window, and self-signed status; a brand-new, self-signed, or mismatched-CN certificate on an otherwise unremarkable destination is a common C2 tell. |
| Beacon interval and jitter | Regular, low-jitter connection timing to the same destination is a classic C2 heartbeat pattern, distinguishable from human browsing behavior. |
Related ports
- 80/tcp: HTTP (Hypertext Transfer Protocol)
- 8443/tcp: HTTPS Alternate (registered as PCsync HTTPS)
- 3128/tcp: Squid HTTP Proxy (de facto; registered as ndl-aas)
- 1080/tcp: SOCKS Proxy
ATT&CK techniques
- T1071.001: T1071.001