Website Availability Checker
Pricing
from $0.60 / 1,000 url checkeds
Website Availability Checker
Check whether websites are up: HTTP status, response time, redirects and the reason a site is down, for any list of URLs. Schedule it to use as a simple uptime monitor.
Pricing
from $0.60 / 1,000 url checkeds
Rating
0.0
(0)
Developer
Mina
Maintained by CommunityActor stats
1
Bookmarked
3
Total users
0
Monthly active users
8 days ago
Last modified
Categories
Features
Share
What does Website Availability Checker do?
Website Availability Checker tells you whether your websites are up and how fast they answer. Give it a list of URLs, and for each one it saves whether the site is available, the HTTP status code, the response time, whether it redirected and where it ended up, plus the reason in plain words when a site is down: the domain doesn't exist, the connection was refused, the request timed out, or the server returned an error. Schedule it on Apify and it becomes a simple uptime monitor.
Try it with the prefilled URLs: open the Actor, click Start, and the results for google.com and github.com appear in the Output tab. Because it runs on the Apify platform, you also get API access, scheduled runs, integrations (Google Sheets, Make, Zapier, webhooks) and run monitoring, so there is nothing to install or host.
Why use Website Availability Checker?
- Uptime monitoring: schedule runs as often as you need and keep a record of when your sites, landing pages or APIs were down.
- Bulk URL checks: find dead links, expired domains and broken pages in a long list of URLs.
- Redirect audits: see which addresses redirect and where they end up, for example after a site migration or a domain change.
- Response time checks: compare how quickly different sites or servers answer.
- List cleanup: drop websites that no longer exist from a list of companies, partners or leads.
How to check website availability
- Enter the addresses to check in Websites to monitor, one per line.
example.comworks too:https://is added for you. - Click Start.
- Watch the results arrive in the Output tab, one row per URL, with
availableset to true or false. - To monitor uptime, save your input as a task and create a Schedule in Apify Console that runs it as often as you need.
- Download the results, or read them through the API.
Input
Everything is set on the Input tab. In JSON, the input looks like this:
{"urls": ["https://google.com","https://github.com","example.com"]}
| Field | Type | Default | What it does |
|---|---|---|---|
urls | array of strings | (required) | Website addresses to check. An address without http:// or https:// is checked over https://. |
Output
One row per URL, in the order you entered them. Real rows from the prefilled run:
[{"url": "https://google.com","originalUrl": "https://google.com","status": "Available","statusCode": 200,"responseTime": "259ms","error": null,"timestamp": "2026-10-13T19:48:13.216Z","available": true,"redirected": true,"finalUrl": "https://www.google.com/"},{"url": "https://github.com","originalUrl": "https://github.com","status": "Available","statusCode": 200,"responseTime": "22ms","error": null,"timestamp": "2026-10-13T19:48:13.542Z","available": true,"redirected": false,"finalUrl": "https://github.com/"}]
A site that can't be reached gets a row too. For a domain that doesn't exist, it looks like this (illustrative values):
{"url": "https://no-such-site-example-12345.com","originalUrl": "no-such-site-example-12345.com","status": "DNS Resolution Failed","statusCode": null,"responseTime": "41ms","error": "Domain not found","timestamp": "2026-10-13T19:48:14.020Z","available": false,"redirected": false,"finalUrl": null}
You can download the dataset in various formats such as JSON, HTML, CSV, or Excel, or read it through the Apify API.
Data fields
| Field | Type | Description |
|---|---|---|
url | string | The address that was checked, with https:// added when it was missing. |
originalUrl | string | The address exactly as you entered it. |
available | boolean | True when the site answered with a 2xx or 3xx status code, after following redirects. |
status | string | The result in words, such as Available, Client Error (4xx), Server Error (5xx), DNS Resolution Failed, Connection Refused, Timeout or Network Error. |
statusCode | integer or null | HTTP status code of the final response. Null when the site did not answer. |
responseTime | string | Time from sending the request until the page had downloaded (its first 10 MB at most), redirects included, as text such as 259ms or 1.23s. For a site that did not answer, the time until the check failed. |
redirected | boolean | True when the final address differs from the one checked. |
finalUrl | string or null | The address after redirects. Null when the site did not answer. |
error | string or null | Why the site did not answer, such as Domain not found, Connection refused by server, Request timed out, or the network error's own message. Null whenever the site answered, even with a 4xx or 5xx code: see status and statusCode then. |
timestamp | string | When the check started (ISO 8601, UTC). |
How much does it cost to check website availability?
You pay per URL checked: each URL you enter is one row in the dataset, whether the site turns out to be up or down. See the Pricing tab for the exact price. The price per URL drops on higher Apify plans, and the Pricing tab lists each tier. Each run also has a tiny charge when it starts, counted per GB of memory with a minimum of one; the Actor runs on 256 MB by default, so that stays at the minimum. The Actor stops by itself when a run reaches the maximum cost you set for it.
Tips for checking website availability
- Keep the default 256 MB of memory. URLs are checked one after another and each check waits on the network, so more memory won't make a run noticeably faster; it only raises the start charge.
- Remove duplicates first. Every line is checked and charged, including repeats.
- Dead sites slow a run down. The Actor waits up to 30 seconds for a site
to answer before reporting
Timeout, so a list with many unreachable sites takes longer. - Redirects: up to 5 redirects are followed. An address that redirects
more often than that is reported as a
Network Error. - Sorting by speed:
responseTimeis text (259ms,1.23s), so convert it to a number before sorting it in a spreadsheet. - Keeping a history: each run saves its results to its own dataset. To build an uptime history, collect the datasets through the API or an integration such as Google Sheets.
FAQ, disclaimers, and support
A site works in my browser, so why is it a Client Error? Some sites
block automated requests or visitors from cloud servers and answer with a code
such as 403 or 429, even though they work in a browser. The Actor checks from
Apify's servers without a proxy, so it reports the code those sites send.
Does it send downtime alerts? Not by itself. Each run saves its results;
to be notified, connect the run to an integration (Make, Zapier or a webhook)
and act on rows where available is false.
Does it check what's on the page? No. It checks the status code, redirects and response time only, not the page's content or keywords.
How does it check a site? It sends one ordinary GET request per URL, with the headers a desktop Chrome browser sends, much as a visitor opening the page would. It can't check from a chosen country.
Is it legal? The Actor makes one normal request per address and collects no data from the pages. Check sites you own or have a reason to monitor, and don't schedule runs so often that they burden someone else's server.
Found a bug or need another field? Open an issue on the Issues tab and it will be looked at. Need a custom tool or a different output format? Get in touch through the Issues tab too.