Website Up & Link Checker: Status, Redirects, Response Time

Use when…

• You need HTTP status, redirects and response time for one or many URLs.
• An uptime or QA agent must confirm pages are up and links are not broken.
• You want a bulk link check with clear ok/fail rows for automation.

Try this input

Copy-paste this JSON as the Actor input (it matches a successful run / the default schema):

{
  "requests": [
    {
      "url": "https://apify.com"
    },
    {
      "url": "https://github.com/apify"
    },
    {
      "url": "http://apify.com"
    },
    {
      "url": "https://httpbin.org/status/404"
    }
  ]
}

Sample output (real run 2026-10-26)

One dataset item, shortened:

{
  "url": "https://httpbin.org/status/404",
  "up": false,
  "status": 404,
  "result": "client_error",
  "response_ms": 13,
  "total_ms": 13,
  "final_url": "https://httpbin.org/status/404",
  "redirected": false,
  "redirect_count": 0,
  "redirect_chain": [
    {
      "url": "https://httpbin.org/status/404",
      "status": 404,
      "ms": 13
    }
  ],
  "content_type": "text/html",
  "server": "gunicorn/19.9.0",
  "…": "+3 more keys"
}

An instant "is this link alive?" check before an agent cites, buys from or sends a link.

• up true/false, HTTP status and a plain result: ok, client_error, server_error, blocked_or_auth, timeout, ssl_error, connection_error, redirect_loop
• Response time of the final hop and total time
• Every redirect hop with status and timing; final_url unshortens bit.ly-style links
• Thousands of URLs per run, 10 in parallel
• Safe: public addresses only, each redirect re-checked
• For scheduled down/up alerts use domain-watch; for content changes use page-change-watch

Quick start

Leave the default input (it is prefilled) and click Start:

{"requests": [{"url": "https://apify.com"}, {"url": "https://github.com/apify"}, {"url": "http://apify.com"}, {"url": "https://httpbin.org/status/404"}]}

Send many items in one run (cheaper and faster than one run each). Settings outside requests apply to every item.

Sample output (real run, 26 Oct 2026, default input)

url	up	status	result	response_ms	redirect_count	final_url
https://httpbin.org/status/404	false	404	client_error	18	0	https://httpbin.org/status/404
http://apify.com	true	200	ok	84	1	https://apify.com/
https://apify.com	true	200	ok	124	0	https://apify.com
https://github.com/apify	true	200	ok	467	0	https://github.com/apify

Each row also has redirect_chain (every hop with status and ms), total_ms, content_type, server and checked_at.

Use cases

• Check links are alive before an agent cites or sends them.
• Find broken links in a list of pages, product URLs or bookmarks.
• Unshorten bit.ly-style links to see the real destination.
• Quick status and speed check across all your sites.

Pricing

Pay per event: $0.001 per url check (one url checked). Rows with errors are not charged. No subscription.

FAQ

Does it crawl a whole site? No. It checks the URLs you send. Use a sitemap or crawler tool to get the list first.

Do I need an API key? No.

How many URLs? Thousands per run, 10 checked in parallel.

Limits & failure modes

• Response times are measured from Apify's cloud servers, not from your location.
• Some sites block cloud servers or bots and return 403 (blocked_or_auth) even though they work in a browser.
• One check per run, so it is not continuous uptime monitoring (use domain-watch on a schedule for that).
• Only public addresses are checked; private and local network addresses are refused.
• Sites that block datacentre IPs can look “down” from Apify even when up for users.
• Soft-404 pages that return HTTP 200 are not always detected as broken.

Output

One dataset row per request. Errors come back as a row with error set, so a batch never fails because of one bad item.

Use from AI agents (MCP)

Add it to any MCP client via https://mcp.apify.com?actors=tudorlane/site-up-link-check, or call the Apify API / run-sync endpoint.

Sources and licences

Live HTTP requests only. No third-party data.