Bulk URL Status Checker
Pricing
from $0.05 / 1,000 url checkeds
Bulk URL Status Checker
Check a list of web addresses in bulk: HTTP status code, the full redirect chain, final address, response time, content type and server. Finds broken links, dead domains and redirect loops.
Pricing
from $0.05 / 1,000 url checkeds
Rating
0.0
(0)
Developer
jake mcclure
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 hours ago
Last modified
Categories
Features
Share
Check a list of web addresses in bulk. For each one you get the HTTP status code, every step of its redirect chain, the final address, the response time, the content type and the server.
No browser is used, so it is fast and cheap: thousands of addresses in a few minutes.
Use it to:
- find broken links (404s), dead domains and server errors in a list of URLs
- check that old addresses redirect to the right new ones after a site migration
- spot redirect chains and loops that slow pages down and waste crawl budget
- verify a list of backlinks, affiliate links or ad landing pages still works
- monitor important pages by running it on a schedule
Input
| Field | What it does |
|---|---|
| URLs | One per line. An address without http:// or https:// in front is checked as https. |
| Follow redirects | On by default: each redirect is followed to the final address and every step is reported. Turn it off to see only the first answer and where it points. |
{"urls": ["https://apify.com", "http://github.com", "example.com/old-page"],"followRedirects": true}
Output
One record per address:
{"input": "http://github.com","url": "http://github.com/","result": "ok","httpStatus": 200,"finalUrl": "https://github.com/","redirected": true,"redirectCount": 1,"redirectChain": [{ "url": "http://github.com/", "status": 301 }],"redirectsTo": null,"contentType": "text/html; charset=utf-8","contentLength": null,"server": "github.com","lastModified": null,"responseTimeMs": 212,"method": "HEAD","error": null,"scrapedAt": "2026-11-18T12:00:00.000Z"}
resultisok(2xx),redirect(a redirect that was not followed),client_error(4xx, such as 404),server_error(5xx) orunreachable(nothing answered: dead domain, timeout, refused connection, certificate problem or a redirect loop).httpStatusis the status of the final address.redirectChainlists each redirect on the way there, in order, with its own status.redirectsTois filled only when redirects are not followed.responseTimeMsis the time to the first answer, added up over the redirects.errorexplains anunreachableresult in plain words, for exampleDomain not foundorTimed out.
A SUMMARY record in the run's key-value store counts how many addresses were fine, broken and unreachable.
Pricing
Pay per result. You are charged once for each address checked, at the per-result price shown on this page, however many redirects it has. Lines that are not web addresses and repeated addresses cost nothing. The run stops as soon as it reaches the maximum charge you set for it.
Limits
- Each address is asked with a lightweight HEAD request. If the server refuses that or reports an error, it is asked once more with a normal GET, so a page is not called broken just because the server dislikes HEAD.
- Requests to the same site are spaced half a second apart, so a long list of pages on one site takes longer than the same number of pages across many sites.
- Up to ten redirects are followed. Redirects made by JavaScript or a
<meta>tag inside the page are not seen. - Some sites answer automated requests differently from a browser (for example with 403). The Actor identifies itself honestly and reports what it was told; it does not disguise itself to get a different answer.
- Each request waits at most 20 seconds.
Is this allowed?
The Actor asks each address the same question a browser asks before loading a page, once, and downloads nothing. It identifies itself in its User-Agent and paces its requests.