This is driving me nuts and saw this earlier thread : SSL Certificate is invalid or missing intermediate (bundle) certificate
My target custom domain sites were giving me different results, and the reason was, simply:
Yes, apparently the broken chain is normal. It is what it is. You can switch browser or upgrade as said earlier. Or you can keep your browser still and setup an account with Cloudflare.
The not forcing HTTPS in whynopadlock is informational and least of your worries. The htaccess instructions posted earlier from IF and Host2B return status 301 and the More Info from whynopadlock return 302. Pretty sure the browser redirects but why did whynopadlock report otherwise? I have no explanation but maybe the server receiving the request is different from the server processing it? Maybe whynopadlock cannot go beyond that initial step.
I used other ssl checkers online but whynopadlock only was “No Force HTTPS”. If you use a different one, you’ll get a different result:
All in all, these words still hold true: