HTTPS — HTTP inside TLS on TCP, and HTTP/3 over QUIC on the UDP side of the same number.
The TLS handshake authenticates the server with an X.509 certificate and names the target host via SNI, then HTTP/1.1 or HTTP/2 runs inside the encrypted channel; HTTP/3 uses the same port number over UDP with QUIC carrying its own TLS 1.3. This is the default port for essentially every public web service and API, and for a lot of non-web traffic tunneled through it because middleboxes let it pass. On a host, whatever holds 443 is the TLS terminator — a web server, a reverse proxy, or a load balancer agent. An open 443 says almost nothing about what is behind it.
Fine to expose
The intended public port; risk lives in the application behind it and in the TLS configuration, not in the port being open.
$ openssl s_client -connect example.com:443 -servername example.com </dev/null 2>/dev/null | head -20Seen this on your network? Beige Box scans your Wi-Fi and shows every open port on every device — and its Ports tool links straight back here.
Get Beige Box →also available as JSON · Markdown
Corrections or a missing port? Reply @rimrocksystems.