IPCheckIP Space
Port Troubleshooting

Port 443 closed

Port 443 is the standard HTTPS port. If it is closed or timed out, browsers may not be able to open the secure version of the site.

Common causes

Web server stoppedNginx, Apache or app proxy is not listening.Check service status.
Firewall blockedHost firewall or cloud security group blocks 443.Allow inbound TCP 443.
Wrong DNS IPDomain points to a server without HTTPS.Check A and AAAA records.
Private bindingService listens only on localhost.Bind to the public interface or proxy correctly.

Checklist

  1. Confirm the domain resolves to the expected server with DNS Lookup.
  2. Run Port Check for port 443.
  3. Check cloud firewall, host firewall and router forwarding.
  4. Confirm the web server is listening on 443.
  5. After it opens, use HTTP Header Check to confirm HTTPS and redirects.

If port 80 is open but 443 is closed, HTTP may load while HTTPS fails. If 443 is open but the browser still fails, check TLS certificates and HTTP headers next.

On cloud servers, remember there may be more than one firewall: provider security group, host firewall, container network, reverse proxy and application binding. On home networks, router port forwarding and carrier-grade NAT can also block inbound 443. Work from outside the network when testing, because local tests can succeed even when public access fails.

FAQ

Can a website work without port 443?

It can work over HTTP port 80, but modern sites should support HTTPS on 443.

Why does 443 time out instead of refusing?

Timeout often means a firewall silently dropped the connection.

Does a certificate problem close port 443?

No. Certificate errors happen after a TCP connection opens.

Related guides

Port CheckTest live ports.Open Port SecuritySecure public services.Website Not LoadingFull diagnosis path.