Fail

Port 443 is closed

The short version

Start the web server on port 443 or remove these addresses from DNS.

What it means

We connected to port 443 on these addresses and the server refused the connection straight away. Something is there, because the address answered, but nothing is listening for HTTPS on that port. Visitors whose browser picks one of these addresses see an error such as "connection refused" instead of your site.

Why it matters

Almost every visit to a website today uses HTTPS on port 443. Browsers upgrade typed names to HTTPS, links and search results point at HTTPS, and many sites are on the HSTS list, which forbids plain HTTP. When some of your addresses refuse port 443, the visitors sent to those addresses can't reach you at all, and which visitors that is changes from one DNS lookup to the next.

How to fix it

  1. Check which addresses are affected: they are listed in the finding. Compare them with the DNS lookup to see which A and AAAA records point there.
  2. If an address belongs to an old server or a host you no longer use, remove that record from your DNS.
  3. If the address is current, make sure the web server is running and configured to listen on port 443, on IPv4 and IPv6 alike. In nginx that means a listen 443 ssl; line and, for IPv6, listen [::]:443 ssl;.
  4. Behind a load balancer or a CDN, check that its HTTPS listener is switched on and has a certificate.

Check it worked

Run the web port check again with the fresh option. Port 443 should be open on every address, and the TLS column should show a working handshake.