Skip to main content
LowSSL

How to fix: HTTPS Served on Non-Standard Port

HTTPS is being served on a port other than 443. Non-standard ports confuse users, bypass browser HSTS expectations for port 443, and indicate the service may be intended as internal-only.

Why it matters

Non-443 HTTPS bypasses HSTS preload protection (preload entries only cover port 443), and users may not notice the non-standard port in the URL bar, making phishing easier.

HSTS preload entries and browser defaults only apply to port 443 for HTTPS. A service on port 8443 or 4443 does not benefit from preloaded HSTS, so users on those ports are not protected on their first visit.

How to fix it

  1. 1Move public-facing HTTPS to port 443 behind a reverse proxy.
  2. 2Keep non-standard ports bound to internal listeners only.
  3. 3If a non-standard port must be exposed, set an explicit HSTS header for that port.

Code examples

Nginx reverse proxy to non-standard port

nginx
# Expose port 443 publicly, proxy to internal :8443
server {
  listen 443 ssl;
  server_name example.com;
  location / {
    proxy_pass https://127.0.0.1:8443;
  }
}

References

Detected automatically by VulnRadar. The check id is https-unusual-port, stable across every scan so you can filter or diff on it.

See every ssl check

Questions

How severe is HTTPS Served on Non-Standard Port?
VulnRadar rates this low severity in the ssl category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id https-unusual-port, which stays the same between runs so you can filter, diff, or gate CI on it.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for https served on non-standard port

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: HTTPS Served on Non-Standard Port | VulnRadar