You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the host "fancyssl.hboeck.de" I get a note under WWW/TLS:
Server is not compliant with Chrome's CT requirements
Not all TLS connections with this server satisfy Chrome's CT requirements even. This is not necessarily a problem, as CT compliance is only required for certificates issued from May 2018.
It appears to me this is incorrect. The certificate is a standard Let's Encrypt certificate which has SCTs embedded, that should be alright.
I can only guess what triggered this warning, but the host is configured for TLS 1.3 only. Maybe there's some detection of TLS extensions (as CT compliance can both be achieved with a TLS extension or SCTs embedded in certs directly) that is triggered here and causes some logic error.
Furthermore, the last sentence ("This is not necessarily a problem, as CT compliance is only required for certificates issued from May 2018. ") is obsolete, as there are no more valid certificates issued before May 2018. So if there is no CT compliance, there's almost certainly a problem.
The text was updated successfully, but these errors were encountered:
For the host "fancyssl.hboeck.de" I get a note under WWW/TLS:
It appears to me this is incorrect. The certificate is a standard Let's Encrypt certificate which has SCTs embedded, that should be alright.
I can only guess what triggered this warning, but the host is configured for TLS 1.3 only. Maybe there's some detection of TLS extensions (as CT compliance can both be achieved with a TLS extension or SCTs embedded in certs directly) that is triggered here and causes some logic error.
Furthermore, the last sentence ("This is not necessarily a problem, as CT compliance is only required for certificates issued from May 2018. ") is obsolete, as there are no more valid certificates issued before May 2018. So if there is no CT compliance, there's almost certainly a problem.
The text was updated successfully, but these errors were encountered: