Bulk URL Health Checker - Status, Redirects & SSL avatar

Bulk URL Health Checker - Status, Redirects & SSL

Pricing

from $0.55 / 1,000 url checkeds

Go to Apify Store
Bulk URL Health Checker - Status, Redirects & SSL

Bulk URL Health Checker - Status, Redirects & SSL

Check a list of URLs for HTTP status, redirect chains, response time, content type, server and security headers, and the TLS certificate (issuer, expiry, days remaining). Find broken links and expiring certs. No browser.

Pricing

from $0.55 / 1,000 url checkeds

Rating

0.0

(0)

Developer

Scrape Sage

Scrape Sage

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

11 days ago

Last modified

Share

Check a whole list of URLs at once and get, for each one: the HTTP status, whether it is OK or broken, the full redirect chain and final URL, response time, content type and length, server and security headers, and - for https - the TLS certificate (issuer, validity, expiry date and days remaining).

Find broken links, unexpected redirects, slow pages and certificates about to expire across a site, a sitemap, or any URL list. Pure HTTP + a TLS handshake, no browser, cents per URL.

What you get per URL

status ok isBroken reachable · responseTimeMs · finalUrl isRedirect redirectCount redirectChain[] · contentType contentLength server poweredBy securityHeaders hsts · sslValid sslIssuer sslValidTo sslDaysRemaining sslError · error.

Input

{
"urls": ["https://apify.com", "example.com/old-page"],
"checkSsl": true
}
  • URLs - one per line; a bare domain gets https://. Leave empty for a small free sample.
  • Import URLs from a file - paste a list, or link a public .txt/.csv, a Google Sheet/Drive link, or an Apify key-value-store record (e.g. pipe a sitemap's URLs straight in).
  • Check TLS/SSL - on by default; turn off for a faster status-only run.
  • Output fields - tick only the columns you need (e.g. just url + status + sslDaysRemaining).

Notes

  • Uses a light HEAD request (falling back to GET when a server rejects it), so it is fast and cheap even on large lists.
  • A URL that does not resolve or times out is reported with reachable: false and the error - that is a valid health result, so every checked URL is counted.

Use with AI assistants (MCP)

Available through the Apify MCP server - an agent can monitor a set of endpoints, audit a site's links, or watch certificate expiry as part of a workflow.

Agent-ready: autonomous payments (x402 & Skyfire)

This actor is agent-ready - AI agents can discover it, run it, and pay for it autonomously, with no Apify account and no human in the loop. It uses pay-per-event pricing and limited permissions, so it qualifies for Apify's agentic-payment standards:

  • x402 - an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the Apify MCP server - no account, no API key.
  • Skyfire - agent-to-service payments for fully autonomous AI-agent workflows.

Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.