Bulk SSL checker
Check certificate expiry across up to 10 hosts in one go. Free, no signup.
You are doing by hand what a schedule should do
Checking ten certificates in a browser works once. WWT checks yours every day and warns you 30, 14, 7, 3 and 1 day before each one expires.
When a bulk check is the right tool
One certificate is easy to keep track of. A dozen across apex domains, www hosts, subdomains and a staging environment is where renewals start slipping, because they were issued at different times by different people and nothing lines them up in one view. Pasting the list here gives you that view in a few seconds: which certificate expires first, which authority issued it, and whether any of them are already failing.
About bulk certificate checks
Why is the limit 10 hosts?
Each host needs its own TLS handshake to somebody else's server. Ten keeps the request fast and keeps us from pointing a burst of connections at other people's infrastructure. If you routinely need more than ten, that is a monitoring job rather than a manual one.
Can I paste a list from a spreadsheet?
Yes. Hostnames can be separated by new lines, commas, semicolons or spaces, so a column pasted straight out of a spreadsheet works as-is.
Why does a host score A here but A+ on the single check?
The bulk check reads certificates only. The single-host check also enumerates the TLS versions the server accepts and reads its HSTS header, and both feed into the grade. Running ten hosts through all of that would be slow and would send far more traffic to servers that did not ask for it.
What does www vs the bare domain change?
They can be entirely different certificates, and often are behind a CDN. Check both if you serve both, because a valid certificate on one says nothing about the other.