Fail

Port 443 is open but the secure connection fails

The short version

Check the certificate and TLS settings on the server; the SSL checker shows the details.

What it means

Port 443 accepts connections on this address, but the secure handshake that starts every HTTPS visit failed, or the server's certificate doesn't name your domain. The result shows the TLS alert the server sent, such as a handshake failure or an unrecognized name, or that the certificate is for another name.

Why it matters

Browsers stop at a failed handshake or a certificate for the wrong name: visitors see a full-page security warning or an error, and most leave. When only some addresses fail, the problem comes and goes depending on which address a visitor gets. Automated clients and APIs refuse the connection outright.

How to fix it

  1. Run the SSL checker on the domain. It shows the certificate, its names, the chain and the TLS versions the server accepts.
  2. If the certificate is for another name, the server is probably sending a default certificate: configure the virtual host for your domain with its own certificate, and check that your domain is listed in its names.
  3. If the handshake fails, check that the server supports TLS 1.2 or 1.3 and a modern cipher suite, and that the certificate and its private key are installed together.
  4. If several servers share the address list, compare their configuration: one of them may have an old or missing certificate.

Check it worked

Run the web port check again with the fresh option. Every open port 443 should show a TLS version and a certificate that names your domain.