Skip to content
Look up and open a port

Port 8443: Check and open the alternative HTTPS port

Port 8443 is a commonly used alternative port for HTTPS, particularly for admin interfaces and application servers. Here you’ll find key details about the port and ready-to-use firewall commands.

Built by Justin Schuessler

Try the commands on your own VPS, with root access and your own firewall.

Add multiple ports one at a time, up to 12.

Or choose a preset

Ports

8443/TCPHTTPS-Alternative

Web · Registered port · OSI layer 7

Common alternative port for HTTPS, for example for Plesk or Tomcat. IANA has registered it for a different service.

IANA: commonly used, but unofficial (registered as pcsync-https)

Firewall rule (inbound)

Firewall commands

Open port

sudo ufw allow 8443/tcp
Check port
Notes on ufw

For Ubuntu and Debian. ufw creates the rule for both IPv4 and IPv6. If ufw is disabled, allow SSH first (sudo ufw allow 22/tcp), then enable it with sudo ufw enable, or you'll lock yourself out.

On a ZAP-Hosting VPS with an active network firewall, you also need to allow the port in the Customer Panel.

Port 8443 explained

What is port 8443 used for?

Purpose

Port 8443 typically hosts web interfaces that need to be accessible over HTTPS without using port 443. Examples include the Plesk admin panel and the Apache Tomcat TLS connector. This lets the main website run on port 443 while the admin interface remains separately accessible on 8443. Traffic is encrypted with TLS, just like on port 443.

Origin and standard

The IANA officially registers port 8443 under the name “pcsync-https”. Its use as an HTTPS alternative is widespread but not officially designated. The number is based on 443, just as 8080 is based on 80. Technically, the port carries the same HTTPS as port 443: HTTP over TLS as defined in RFC 2818 and RFC 8446.

Typical use

  • Admin panels such as Plesk
  • TLS connector for Apache Tomcat and other Java application servers
  • Management interfaces for network devices and controllers
  • A second HTTPS service alongside a website on port 443

Security

Port 8443 usually hosts an admin interface, a popular target for brute-force attacks and exploits. Whenever possible, allow access only from your own IP address or through a VPN. Enable two-factor authentication if the panel supports it, and keep the software up to date. Many panels initially use a self-signed certificate. Replace it with a valid certificate so you do not have to dismiss browser warnings.

More ports

Related ports

These ports are often part of the same setup. Click one to see its explanation and firewall commands.

View all well-known ports and the complete IANA list

Port list source: IANA Service Name and Transport Protocol Port Number Registry, as of October 22, 2026. iana.org

Discover more

More tools

FAQ

Frequently asked questions

Quick answers about port 8443.

No. The IANA lists port 8443 under the name “pcsync-https”. It is nevertheless widely used as an alternative HTTPS port, including by Plesk and Tomcat.

With ufw, use sudo ufw allow 8443/tcp. With firewalld, open the port using sudo firewall-cmd --permanent --add-port=8443/tcp and reload the rules using sudo firewall-cmd --reload.

In practice, port 8443 uses TCP because HTTPS traditionally runs over TCP. You only need UDP 8443 as well if an application offers HTTP/3 on that port.

Only if you really need to. Since an admin interface is usually running behind it, allowing access only from your IP or using a VPN is much safer.

Any more questions?

Contact Support
Your own server?

Try the commands on your own VPS

With a ZAP-Hosting VPS, you have root access, can set up services and firewall rules yourself, and can immediately see which ports are open.

4.4/5 Trustpilot32,000+ Active serversSince 2010

No setup. No risk. Online in seconds.

Flexible TermCancel anytimeOnline in 60 seconds

Looking for more tools? View all network tools