Check when a domain's SSL/TLS certificates expire: current certificates from public Certificate Transparency logs with issuer, SAN names, days remaining, wildcard flag and a subdomain inventory. Free, no signup.
Enter a hostname and click Check certificates.
Certificate Transparency shows certificates that were issued, not necessarily the one a server presents today (an old certificate can still be installed after a renewal, or a load balancer can serve a different one). To read the live certificate, run this from any machine with OpenSSL:
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -subject -issuer -dates -ext subjectAltName
For a mail server use -starttls smtp -connect mx.example.com:25, and for another port change :443. notAfter is the expiry date.
www.example.com (a URL or email address works too; only the host part is used).openssl s_client command, which updates for the hostname you checked.Look up the CAA records that control which CAs may issue for your domain with DNS Lookup, or check that a new record has reached public resolvers with the DNS Propagation Checker. Securing mail servers? See the MTA-STS Policy Generator.
Enter the hostname above to see every current certificate public CAs have issued for it, with expiry dates and days left. To read the certificate a server is serving right now, run: echo | openssl s_client -connect example.com:443 -servername example.com | openssl x509 -noout -dates and look at notAfter.
Certificate Transparency (CT) is a set of public, append-only logs. Browsers only trust publicly issued TLS certificates that have been logged, so nearly every public certificate shows up in CT within minutes. Cert Spotter and crt.sh index those logs and make them searchable.
A web page cannot open a raw TLS connection to another server, so it cannot read the certificate a server presents. It uses CT logs instead, which list issued certificates. A server can still be serving an older certificate after a renewal, so confirm with openssl s_client or your monitoring.
Under CA/Browser Forum ballot SC-081 the maximum is 200 days for certificates issued from 15 March 2026, then 100 days from 15 March 2027 and 47 days from 15 March 2029. Let's Encrypt issues 90-day certificates, moving to 64 days by default on 10 February 2027 and 45 days on 16 February 2028. Automated renewal (ACME) is the only practical option.
Hosting providers, CDNs, email security gateways and SaaS platforms often request certificates for your names automatically. Unknown issuers or names can also point to shadow IT or a mis-issued certificate. Restrict issuance with a CAA record and review the subdomain inventory regularly.
Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.