Certificate chain
The server certificate, intermediate authorities and root trust path are displayed in their actual order.
Verify certificate installation, hostname matching, browser trust, expiration, negotiated TLS version and the active cipher suite.
The server certificate, intermediate authorities and root trust path are displayed in their actual order.
Validity dates, remaining days, hostname matching and trust status are evaluated.
The negotiated TLS protocol, public-key size, signature algorithm and cipher suite are reported.
A valid leaf certificate is not enough. The chain must be complete, the hostname must match and a secure protocol must be negotiated. Missing intermediate certificates can break APIs, older clients and embedded devices even when a desktop browser appears to work.