What it means
We tried to open a secure connection to your domain, and its www name when you checked a bare domain, on port 443, the standard HTTPS port. None of them completed: the name has no address, the server refused the connection, it answered with something other than TLS, or the handshake failed. The detail says what happened for each host name.
Why it matters
Browsers mark plain HTTP sites as not secure, and many now try HTTPS first and show a warning when it fails. Search engines favour HTTPS sites, and features such as passwords, payments, location and service workers require it. Without HTTPS, anyone on the network path can read and change your pages.
How to fix it
- If the name has no address, add an A record pointing at your web server, or set the name up with your hosting provider.
- Make sure the server listens on port 443. A firewall or security group often blocks it while port 80 is open.
- Install a certificate for every name visitors use. Let's Encrypt is free, and most hosting providers turn it on with one click.
- Once HTTPS works, redirect plain HTTP to HTTPS.
Let's Encrypt with certbot
sudo certbot --nginx -d example.com -d www.example.com gets a certificate, configures port 443 and adds the
redirect. Use --apache for Apache.
Cloudflare
Proxy the names through Cloudflare (the orange cloud) and set SSL/TLS to Full (strict) with a certificate on your server.
Check it worked
Run the SSL check again. At least one card should say "Trusted" and the finding should be gone.