Port 8443 — HTTPS alternate
TCP registered
What runs on port 8443
The unprivileged counterpart to 443, used by Tomcat and many appliances.
Security considerations
Same exposure as 443 — treat it identically.
Checking whether something is listening
# Linux / macOS — what is bound to the port
sudo lsof -i :8443
sudo ss -lntp | grep :8443
# Windows
netstat -ano | findstr :8443
Get-NetTCPConnection -LocalPort 8443
# is it reachable from outside?
nc -zv example.com 8443
curl -v telnet://example.com:8443
Freeing the port
# find the process, then stop it
sudo lsof -ti :8443 | xargs kill # Linux / macOS
netstat -ano | findstr :8443 # note the PID, then:
taskkill /PID <pid> /F # Windows
Should this port be open to the internet?
Yes — that is what it is for. Make sure whatever is listening is something you intend to expose, and that TLS is configured properly.
Quick reference
| Port | 8443 |
| Protocol | TCP |
| Service | HTTPS alternate |
| Range | Registered (1024–49151) — any user process may bind |
Frequently asked questions
What is port 8443 used for?
The unprivileged counterpart to 443, used by Tomcat and many appliances.
Is it safe to open port 8443?
Same exposure as 443 — treat it identically.
How do I check if port 8443 is open?
Locally, sudo lsof -i :8443 on macOS or Linux, or netstat -ano | findstr :8443 on Windows. From outside, nc -zv host 8443 tells you whether anything answers.
Why do I get "address already in use" on port 8443?
Another process is bound to it — often a previous run of your own program that did not exit cleanly. Find it with lsof -ti :8443 and stop it, or configure your application to use a different port.
Can I change the port this service uses?
Almost always yes, in the service's configuration. Moving off a default port reduces automated scan noise, but it is obfuscation rather than security — a real attacker scans all 65,535.