What it means
Your domain has several addresses, and port 443 answers on some of them but not on others. Each visitor's browser picks one address, so some people reach your site and others get an error or a long wait. To you the site may look fine, because your own connection happens to use a working address.
Why it matters
Partial outages are hard to notice and hard to report. Visitors describe them as "the site is down sometimes", and a reload may land on a working address. Search engines and monitoring services see the same lottery. One stale record from an old server or a retired load balancer is enough to turn a fraction of visits into errors.
How to fix it
- Note the failing addresses listed in the finding, and compare them with the A and AAAA records in the DNS lookup.
- For each failing address, decide whether it should still be in use. A leftover address from a previous host or a server that was shut down should simply be removed from DNS.
- If the address should work, fix the server behind it: start the web server, open port 443 in its firewall, and check that it has the same configuration and certificate as the working servers.
- If the addresses belong to a load balancer or CDN, contact the provider: one of its nodes may be unhealthy.
Check it worked
After the old TTL has passed, run the web port check again with the fresh option. Every address should show port 443 open, and this finding should be gone.