Bulk SSL/TLS Checker 🔐 — HTTPS Reachability, Certificate Status & TLS Audit (No API)

Check SSL/TLS and HTTPS reachability for thousands of domains in a single run. Paste a list of domains and this bulk SSL checker connects to each one over HTTPS (port 443), performs the TLS handshake, and returns a clean row with TLS reachability, HTTP status code, response latency, final redirect URL and a classified error type — so you instantly know which hosts are HTTPS-healthy and which are broken. No API key, no external SaaS, no SSL Labs rate limits — pure client-side TLS probing.

🏆 Why this SSL/TLS checker?

Thousands of domains per run · TLS handshake + HTTPS reachability in one pass · TLS errors classified separately from timeouts and DNS failures · direct connection (no third-party API) · export to JSON / CSV / Excel. The unofficial SSL checker API alternative for HTTPS monitoring, uptime canaries and security audits — with no API key.

---

✨ What this Actor does / Key features

• 🔐 Bulk TLS + HTTPS probing — connect to thousands of domains over HTTPS in a single parallel run.
• 📡 Reachability at a glance — hasTls tells you whether the host completed a TLS handshake and served content over HTTPS.
• 🔢 HTTP status + latency — capture the returned statusCode and the round-trip latencyMs for every domain.
• 🔀 Redirect resolution — follows up to 3 redirects and reports the finalUrl the host resolves to.
• 🧠 Smart error classification — failures are bucketed as tls_error, timeout, connection_error or unknown, so a cert problem is never confused with a DNS or timeout issue.
• ⚡ High concurrency — configurable parallel connections (default 10, up to 100) for fast bulk scans.
• 🧹 Robust input parsing — schemes (https://), paths, ports and trailing dots are stripped automatically; duplicates removed.
• 🛡️ No API key, no SaaS — everything runs client-side in the Apify runtime; no SSL Labs dependency, no external rate limits.
• 💾 Export anywhere — download as JSON, CSV, Excel or XML, or pull via the Apify API.

🚀 Quick start (3 steps)

1. Configure — paste your domain list into Domains, one per line (example.com or https://example.com/path both work).
2. Run — click Start. The Actor probes every domain over HTTPS in parallel and streams one row per domain into your dataset.
3. Get your data — open the Output tab and export to JSON, CSV, Excel or XML, or pull it via the Apify API.

📥 Input

Give the Actor at least one entry in domains. Everything else is optional.

Example — audit a portfolio of company domains

{
  "domains": ["google.com", "github.com", "stackoverflow.com", "wikipedia.org"],
  "maxConcurrency": 10,
  "proxyConfiguration": { "useApifyProxy": true }
}

Example — flag broken / misconfigured HTTPS (mix of good & bad hosts)

{
  "domains": ["expired.badssl.com", "self-signed.badssl.com", "wrong.host.badssl.com", "example.com"],
  "maxConcurrency": 20,
  "proxyConfiguration": { "useApifyProxy": true }
}

Example — fast large-list reachability scan

{
  "domains": ["shop.example.com", "api.example.com", "cdn.example.com", "mail.example.com", "legacy.example.com"],
  "maxConcurrency": 50,
  "proxyConfiguration": { "useApifyProxy": true }
}

Field	Type	Description	Default
domains	array	Domains (or full URLs) to check. Schemes, paths, ports and trailing dots are stripped automatically; duplicates removed. Required.	–
maxConcurrency	integer	Parallel HTTPS connections. Higher is faster but may overwhelm small servers or trip rate limits.	10 (min 1, max 100)
proxyConfiguration	object	Apify Proxy settings for the outbound connections. Recommended to avoid IP-based rate limiting.	Apify Proxy (datacenter)

Tip: Provide bare domains (example.com) for the cleanest results, but subdomains (api.example.com) and full URLs both work — the Actor normalizes them for you.

📤 Output

One row per domain, exportable to JSON, CSV, Excel or XML. Here is a trimmed sample record for a healthy host:

{
  "domain": "github.com",
  "hasTls": "true",
  "statusCode": "200",
  "latencyMs": "312",
  "finalUrl": "https://github.com/",
  "error": null,
  "checkedAt": "2026-07-06T12:00:00.000Z"
}

And a row for a domain with a certificate problem — note the classified errorType:

{
  "domain": "expired.badssl.com",
  "hasTls": "true",
  "statusCode": null,
  "latencyMs": "1084",
  "finalUrl": null,
  "error": "certificate has expired",
  "errorType": "tls_error",
  "checkedAt": "2026-07-06T12:00:00.000Z"
}

💡 Use cases

• HTTPS uptime & reachability monitoring — run on a schedule against your domain portfolio and flag any host that stops serving over HTTPS (hasTls: "false") before customers notice.
• Certificate-problem detection — filter by errorType: "tls_error" to surface expired, self-signed, hostname-mismatch and other TLS misconfigurations across all your assets at once.
• Security & compliance audits — inventory which of your public-facing hosts are HTTPS-healthy and which fail, as evidence for audits and remediation tickets.
• Migration & cutover checks — after a DNS or infra change, bulk-verify that every domain still resolves over HTTPS and returns the expected statusCode and finalUrl.
• Vendor & competitor posture checks — quickly see whether a set of third-party domains serve valid HTTPS and how fast they respond (latencyMs).
• DevSecOps canaries — schedule recurring runs and diff datasets to catch unexpected HTTPS breakages or status-code drift.

👥 Who uses it

DevOps & SRE teams monitoring HTTPS uptime · security engineers running TLS posture audits · IT admins managing large domain portfolios · penetration testers & bug-bounty hunters triaging hosts · compliance analysts collecting HTTPS evidence · agencies auditing client infrastructure at scale.

💰 Pricing

This Actor runs on a simple pay-per-result model — you pay for the domains you check, with no separate Apify platform fees to calculate. Try it on the free tier first, then scale up. See the Pricing tab on this page for the current rate.

❓ Frequently Asked Questions

How do I check SSL/TLS for many domains at once? Paste your full domain list into the Domains field and run the Actor once. It connects to every domain over HTTPS in parallel and returns one row per domain with reachability, status code, latency and any error.

Is this an SSL checker API alternative? Yes. Instead of calling a third-party SSL SaaS or SSL Labs (which imposes strict rate limits), this Actor performs the TLS handshake itself from the Apify runtime — so it works as an unofficial SSL checker API alternative with no API key and no external rate limits.

Can I check SSL/TLS without an API or login? Yes. There is no external account, login or API key required — only an Apify account. The Actor probes publicly reachable hosts over standard HTTPS.

What does hasTls actually mean? It reports whether the host completed a TLS handshake and served content over HTTPS. A host that fails specifically with a certificate/TLS error is still marked hasTls: "true" (TLS is present but broken), while DNS failures, refused connections and timeouts are marked hasTls: "false".

How are errors classified? Every failed row includes an errorType: tls_error (certificate/TLS handshake problem), timeout (host too slow), connection_error (DNS failure or refused connection), or unknown. This lets you separate certificate issues from network issues instantly.

What happens with a domain that has no HTTPS (HTTP-only)? The HTTPS connection fails, and the row is logged with hasTls: "false" and the reason in the error/errorType fields. The run never crashes — every domain always produces a row.

How much data can I get / how many domains can I check? You can check thousands of domains per run. Increase maxConcurrency (up to 100) for large lists; each domain produces exactly one output row.

How do I export SSL check results to CSV or JSON? Run the Actor, then export the resulting dataset as CSV, JSON, Excel or XML from the Apify Console or via the Apify API — one domain per row, ready for spreadsheet filtering.

Is it legal to run bulk SSL checks? The Actor only performs standard HTTPS connections to publicly reachable hosts — the same thing any web browser does. You are responsible for scanning only domains you are authorized to test and for complying with applicable terms and laws.

🔗 More website & DevSecOps tools by logiover

Building an infrastructure-audit or recon pipeline? Pair this SSL checker with the rest of the website-intelligence suite:

Tool	What it does
Bulk HTTP Security Headers	Scan CSP, HSTS, X-Frame-Options and score security posture of any URL
Bulk DNS Records Lookup	Resolve A, AAAA, MX, TXT, NS, CNAME, SOA, CAA via DNS-over-HTTPS
Bulk URL Status Checker	HTTP status codes and redirect chains for large URL lists
Bulk WHOIS / RDAP Lookup	Registrar, creation/expiry dates and nameservers per domain
Bulk Email Deliverability Checker	MX, SPF, DKIM, DMARC and BIMI audit per domain
Bulk Email Verifier	Validate email addresses in bulk (syntax, MX, deliverability)
Subdomain Finder	Discover subdomains via Certificate Transparency logs
Certificate Transparency Monitor	Watch CT logs for newly issued certificates on your domains
Website Tech Stack Detector	Fingerprint frameworks, servers and analytics on any site
Website SEO Audit Crawler	Crawl a site and flag on-page SEO and technical issues
Bulk URL Unshortener	Expand shortened URLs and trace their full redirect chains
Website Change Monitor	Detect and diff changes on any web page over time

👉 Browse all logiover scrapers on Apify Store — 180+ actors across real estate, jobs, crypto, social media & B2B data.

⏰ Scheduling & integration

Schedule this Actor on Apify to monitor your HTTPS estate daily or hourly. Export results to JSON, CSV or Excel, sync to Google Sheets, or push to your database, BI tools and webhooks through the Apify API. Connect it to Make, n8n or Zapier to build automated alerting when a domain's hasTls flips to "false" or a certificate error appears.

⭐ Support & feedback

Found a bug or need an extra field? Open an issue on the Issues tab — response is usually fast. If this Actor saves you time, a ★★★★★ review on the Store page genuinely helps and is hugely appreciated. 🙏

⚖️ Legal

This Actor performs only standard HTTPS connections to publicly reachable hosts and returns technical reachability metadata. It is intended for legitimate monitoring, security-audit and research use. You are responsible for testing only domains you are authorized to scan and for complying with applicable terms of service and local laws.

---

📝 Changelog

2026-07-06

• ✨ README overhaul: corrected the output field reference to match the actual TLS/HTTPS reachability fields (hasTls, statusCode, latencyMs, finalUrl, errorType), added ready-to-run example scenarios, a website/DevSecOps cross-promo grid, and a clearer quick-start.

2026-07-01

• Maintenance pass: re-verified end-to-end on live data and confirmed successful runs within the 5-minute quality window on the default input.
• Sharpened Store metadata (SEO title & description) and expanded the FAQ with high-intent, long-tail questions for easier discovery in Google and Apify Store search.
• Added ready-to-run example tasks that cover common real-world use cases.

2026-06-24

• Initial release — bulk SSL/TLS + HTTPS reachability inspection (TLS handshake, status code, latency, redirect resolution, classified error types), no API key, CSV/JSON export.