What it contains
The names it covers (for example example.com and www.example.com), the public key, the issuer, the start and end dates of its validity and the issuer’s signature. A browser accepts it only if the name matches the address, the dates include today and the issuer’s signature chains up to a certificate authority it trusts.
Why it matters for a client site
A valid certificate is invisible. An expired or mismatched one stops the connection being trusted, and browsers show a full-page warning. Certificates now have maximum lifetimes that keep shrinking: 200 days from 15 March 2026, falling to 47 days by 2029, so renewal is frequent and mostly automated, which makes watching the result more important.
How to read one
openssl s_client -connect example.com:443 -servername example.com </dev/null 2>/dev/null | openssl x509 -noout -subject -issuer -dates prints the name, the issuer and the validity dates of the certificate a visitor would receive. Run it for each client’s main host, or let a monitor do it, and alert early enough to act: renewal fails most often after a DNS or hosting change, and with HSTS an expired certificate locks returning visitors out.
What to check
The expiry date, the hostnames covered, the issuer, whether the full chain is served and whether the certificate changed unexpectedly. See the guide on certificate expiry for a routine.
Sources
Read on . Standards and vendor pages change; confirm the current text before you rely on it.
- CA/Browser Forum ballot SC-081v3 timeline, as summarised by SecureW2 (securew2.com)
- RFC 6797, HTTP Strict Transport Security (www.rfc-editor.org)