# Lead List Website Check: dead, parked, hijacked, bot-walled (`omenz/lead-list-website-check`) Actor

Bulk-check lead-list websites: live, dead, parked/for sale, hijacked by spam, behind bot protection, moved, JavaScript-only. $0.002 per site.

- **URL**: https://apify.com/omenz/lead-list-website-check.md
- **Developed by:** [Oscar Menz](https://apify.com/omenz) (community)
- **Categories:** Lead generation, Developer tools, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 site checkeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Lead List Website Check

**Is this business's website still alive, still theirs, and readable by a machine?** One boring, fast check per URL, before your pipeline or agent spends a browser session, an email, or a sales call on it.

### What you get per site

`status` is one of:

- **live**: the site answers and looks like a real site
- **parked**: for sale / parked / suspended / coming soon
- **hijacked_spam**: the domain now serves spam (we keep finding local-business domains taken over by gambling spam)
- **redirected_offsite**: ends on a different domain we can't tie back to the business
- **blocked_by_bot_protection**: Cloudflare, Sucuri, etc. refuse automated readers (`blocked_by` says which)
- **rate_limited**, **http_error**, **dead** (no DNS / no response / 404), **invalid_url**

Plus:

- `moved_to`: the business moved to its own new domain (still **live**)
- `js_only`: the page has almost no readable text without JavaScript, so you will need a browser
- `placeholder_name`: a site-builder placeholder left in the site's own name data (e.g. "Your Site Title")
- `name_found`: when you pass a business name, whether it appears on the homepage (`null` if not checked)
- `final_url`, `http_status`, `title`, `notes`

### Input

```json
{ "urls": ["https://example.com"] }
```

or with names:

```json
{ "sites": [{ "url": "https://example.com", "name": "Example Bakery" }] }
```

or point it at a dataset (for example Google Maps scraper results) with `datasetId`. Rows with `website` and `title` fields are read automatically. Up to 1000 sites per run, 10 at a time.

### How accurate is it?

Tested on a frozen holdout of sites it had never seen (graded by hand, rules fixed before the run):

- usable vs not usable: **26 of 26** verified
- exact status label: **25 of 26 (96%)**. The miss: a broken TLS certificate was labelled `dead`

It caught 2 local-business domains hijacked by gambling spam, 2 for-sale domains, and a Cloudflare-walled bookstore.

### Pricing

**$0.002 per site checked** ($2 per 1,000). No subscription.

### Honest limits

- It identifies itself honestly and **never bypasses bot protection**; a blocked site is reported as blocked.
- Labels describe what an automated reader gets, not what a person sees in a browser.
- No phone numbers or other contact data are returned. Public pages only, at most 2 requests per site, no AI calls.

### Feedback

Open an issue on the **Issues** tab: what you're using it for and what you'd want checked next.

Built by OMENZ: https://omenz.org

# Actor input Schema

## `urls` (type: `array`):

Websites to check (max 1000 per run).

## `sites` (type: `array`):

\[{"url": "...", "name": "..."}]. With a name, the check also says whether the business name appears on the site.

## `datasetId` (type: `string`):

Check every row of a dataset that has a 'website' (or 'url') field, e.g. Google Maps scraper results. 'title'/'name' is used as the business name.

## Actor input object example

```json
{
  "urls": [
    "https://example.com"
  ]
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "https://example.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("omenz/lead-list-website-check").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": ["https://example.com"] }

# Run the Actor and wait for it to finish
run = client.actor("omenz/lead-list-website-check").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "https://example.com"
  ]
}' |
apify call omenz/lead-list-website-check --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,omenz/lead-list-website-check"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/SwsmYSeSItOriJKne/builds/OgVxIdjfUD4Rup1xZ/openapi.json