Port 8443/tcp: HTTPS Alternate (registered as PCsync HTTPS)
Category: Web & Application. Range: registered. Status: de facto standard.
What runs here
Port 8443/tcp's IANA registration is literally pcsync-https, registered to Laplink Software for its PCsync file-synchronization product's HTTPS interface, a use that is essentially obsolete today. In current practice 8443 functions the way 8080 does for HTTP: a widely-adopted, unofficial convention as the alternate/non-privileged port for HTTPS, defaulted to by many Java application servers and by network device or appliance admin consoles.
Why it matters
The gap between the official registration (a defunct Laplink sync product) and overwhelming real-world usage (a generic HTTPS admin or API endpoint) is exactly the kind of port an analyst has to fingerprint rather than trust by name. Its common role as an admin-console/management port also makes it a frequent scanning and exploitation target; internal tools left exposed on 8443 are a recurring initial-access vector.
Where you see it
Legitimately: application server SSL connectors, network appliance and device management UIs, alternate HTTPS listeners behind a reverse proxy. Anomalously/maliciously: internet-facing admin consoles left exposed on 8443 and scanned or exploited for default credentials or known CVEs, or an attacker choosing 8443 for a TLS-wrapped C2 listener to resemble a benign management port.
What to look for
| Signal | What it means |
|---|---|
| Certificate CN/SAN and TLS fingerprint | The same triage as 443: check the served certificate and JA3/JA3S to identify the actual product or appliance rather than assuming a benign admin panel. |
Related ports
ATT&CK techniques
- T1071.001: T1071.001