Bulk SSL Checker
Check the SSL certificates of up to 50 hostnames at once and see each one's health, expiry date, days left, issuer and whether the chain is complete. Paste one hostname per line, such as example.com and api.example.com.
- Free
- No signup required
- Live TLS connections
Common problems in an SSL audit
Forgotten subdomains expiring
The main site renews automatically, but staging, an old marketing page or an API hostname uses a certificate someone installed by hand years ago. Sort by days left and deal with anything under 30 days first.
Incomplete chain on some servers only
A load-balanced or multi-server setup where one machine was configured with the certificate alone. The table shows the chain column per hostname, so one broken server stands out. Install the full chain on it and reload.
Different issuers where you expected one
A hostname still shows an old commercial CA, or a control panel's default certificate, after you moved everything to Let's Encrypt or a CDN. The issuer column makes those leftovers easy to spot.
Hostname fails to connect
The name no longer resolves, the server is down, or nothing listens on 443. Decide whether the hostname is still needed. If not, remove its DNS record so it cannot be taken over or left serving something stale.
Wildcard certificate renewed but not deployed everywhere
A wildcard such as *.example.com is renewed on one server but the old copy stays on others. Hostnames that share a certificate should show the same expiry date; one that lags is still on the old file.
How to check SSL certificates in bulk
- Paste up to 50 hostnames, one per line. Add :port for services on another port.
- Click Check all.
- Sort by days left to see what expires first, and look for incomplete chains.
- Download the table as CSV to share it or keep it as an audit record.
What does a bulk SSL check show?
A bulk SSL check runs the same test as the SSL Checker on every hostname in your list: it connects like a strict client, using only the certificates each server sends, and reads the certificate it gets back.
For each hostname you see the health verdict (Healthy above 30 days, Warning at 30 days or fewer, Critical at 7 days or fewer, or Expired or Invalid), the expiry date, the days left, whether the chain is complete, and the issuer. Sorting by days left turns a list of domains into a renewal schedule.
Checking in bulk matters because certificates rarely fail where you look. The main site gets attention. The certificate that expires is on the status page, the old API hostname or the client site nobody has opened in a year.
Every 10 hostnames count as one check toward the daily free allowance.
example.com www.example.com api.example.com mail.example.com:993
When to use a bulk SSL checker
Agencies with many client sites
Check every WordPress or Shopify site you look after in one pass and send each client a CSV of what needs attention.
Auditing subdomains before a migration
Before moving DNS to Cloudflare or a new host, record the certificate state of every subdomain so you can compare it after the move.
Monthly certificate review
Paste the same list each month, sort by days left and renew anything that is not renewing itself.
After rolling out a new wildcard certificate
Confirm every server picked up the new expiry date and the full chain.
Check something else
- SSL CheckerCheck a site's SSL certificate, expiry date and whether the intermediate certificate is installed.
- TLS Version CheckerSee which TLS versions a server accepts, from TLS 1.0 to TLS 1.3, and the cipher it picks for each.
- Domain Expiry CheckerSee exactly when a domain expires and how many days are left before renewal.
- Website Down CheckerCheck if a website is down for everyone or just you, with status code, response time and final URL.
Frequently asked questions
How many hostnames can I check at once?
Up to 50 per run. Every 10 hostnames count as one check toward the daily free allowance.
Can I include a port?
Yes. Write the hostname with a colon and the port, such as mail.example.com:993. Without a port, 443 is used.
What does chain complete mean?
The server sent every intermediate certificate needed to reach a trusted root. If it is not complete, browsers may still work but curl, apps and API clients will refuse the connection.
What is in the CSV download?
The results table, one row per hostname: health, expiry date, days left, whether the chain is complete, and issuer. Open it in Excel or Google Sheets, or keep it as an audit record.
Why is a hostname shown as failed?
The checker could not complete a TLS connection: the name does not resolve, the server is down, nothing answers on that port, or the server is not using TLS there.
Fifty sites for US$47 a year
Checking a list once a month leaves 29 days for something to break. Import your hostnames into TinyPing from CSV and each one is watched for you, with an alert when:
- a certificate is 14, 7, 3 or 1 days from expiring
- an expired or broken certificate makes HTTPS fail
- a site returns an error or times out
US$6.99 a month or US$47 a year per 50 monitors, team members free. 7-day free trial, no card needed.
Want alerts in team chat? Follow the guide for Slack or Google Chat.