What it means
People reach a site four ways: http:// and https://, each with and without www. One of
those has an address but fails: the connection is refused, times out, the secure connection fails or the
server answers with a 5xx error. The detail lists the entry points that failed.
Why it matters
Visitors type addresses in every form, links in old emails and documents use whichever form was current, and some browsers try HTTPS first. Each broken entry point loses a share of visitors and looks like an outage to them. It also often means a certificate covers only one of the names.
How to fix it
- Look at the entry point that failed and its outcome in the result.
- If the connection is refused or times out, make sure the web server (or CDN) listens on that port for that name, and that no firewall blocks it.
- If the secure connection fails, get a certificate that covers both names, for example with
certbot -d example.com -d www.example.com. - If it answers with a 5xx error, check the server logs for that host name.
- Redirect the working entry points to one canonical address.
Check it worked
Run the HTTP and security headers check again. All entry points with an address should end on a page, and the finding should be gone.