What it means
We check your domain and its www name. One of them completes a secure connection; the other has an address but doesn't: the server refuses the connection on port 443, answers with something other than TLS, or the handshake fails. The detail names the host that doesn't work.
Why it matters
People type both forms, and old links and other sites use both. Visitors who arrive on the broken name get an error or a warning instead of your site, even though the site itself is fine. It often happens when www points at a different server or service than the bare domain.
How to fix it
- Check where the broken name points: run a DNS lookup and compare its address with the working name's.
- If both should reach the same server, point the broken name there too, for example with a CNAME from www to the bare domain.
- Make sure the certificate on that server lists both names, and that the server listens on port 443 for both.
- If the name should not serve the site, keep HTTPS working on it and redirect it to the main name.
Let's Encrypt with certbot
Include both names when you request the certificate: sudo certbot --nginx -d example.com -d www.example.com.
Hosting providers
Many hosts treat www as a separate domain. Add it in the control panel so the host issues a certificate for it and serves the site there.
Check it worked
Run the SSL check again. Both cards should say "Trusted".