Damn. Sorry to see that this service was running at a loss. I have a service that, among other things, checks SSL certificates: DomainProactive (https://domainproactive.com). Please try it out if you have this need. - Source: Hacker News / about 2 years ago

I find that many sites implement HSTS and the redirect to HTTPS wrong. For example, they will have http://example.com redirect to https://www.example.com instead of first redirecting to https://example.com. This leaves that first request still open to attack. [Kind of a plug: I made a test for this in my tool, DomainProactive (https://domainproactive.com). I would appreciate feedback on this kind of error.]. - Source: Hacker News / over 2 years ago

I built DomainProactive: https://domainproactive.com. Source: over 2 years ago

Check it at https://ssllabs.com/ssltest and it will tell you what’s wrong with the chain. Source: about 1 year ago

Didn’t know that one. I generally use ssl server test at https://ssllabs.com/ssltest. Source: over 1 year ago

As far as the SSL error, your browser does not consider the certificate to be valid. It looks like you’re trying to use Let’s Encrypt (based on your .well-known/acme-challenge location. You’ll also need to provide the intermediary certificate, but there also may be something else wrong (e.g., are you using the staging CA and not the production CA when brokering the certificate?). I can’t tell what’s wrong without... Source: over 1 year ago

If you want to prove it, check your site with https://ssllabs.com/ssltest. It checks web servers for safe TLS configurations, including whether or not you have TLS compression enabled. Source: about 2 years ago

Try running SSL test on server. https://ssllabs.com/ssltest/ It reports incomplete certificate. Did you add whole chain on "ssl_certificate" file? Root cert is not needed but intermediate should be in there with server certificate. Source: about 2 years ago