# Wayback Machine Domain History & Age Checker (Bulk) (`zhucl1006/wayback-domain-history-age-checker`) Actor

Bulk-check website age and archive history from the Wayback Machine: first & last snapshot, age in years, active years, gap years, captures per year and yearly snapshot links. For SEO, expired-domain buying, due diligence and lead scoring.

- **URL**: https://apify.com/zhucl1006/wayback-domain-history-age-checker.md
- **Developed by:** [leo zhu](https://apify.com/zhucl1006) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 result items

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

## Wayback Machine Domain History & Age Checker (Bulk)

Paste a list of domains and get, for each one, its **archive history from the Internet Archive Wayback Machine**: when the website first appeared, when it was last captured, how old it is, in which years it was active, gap years (dropped / parked periods) and links to one snapshot per year.

Uses the Internet Archive's public **Availability API** and **CDX API** - no login, no browser, no scraping of archived pages.

### Who it's for

- **SEO & expired-domain buyers**: check domain age and continuous history before buying; gap years often mean the domain dropped and was re-registered.
- **Due diligence / investors / M\&A**: how long has this company really had a website?
- **Sales & lead scoring**: older websites usually mean established businesses - add `ageYears` to your lead list.
- **Fraud & trust checks**: brand-new websites that claim "20 years in business".

### Input

```json
{ "domains": ["apify.com", "python.org", "stripe.com"], "includeYearlySnapshots": true, "onlySuccessfulCaptures": true }
```

### Output (one row per domain)

```json
{
  "domain": "apify.com",
  "status": "ok",
  "firstSnapshot": "2007-05-31T10:15:38+00:00",
  "firstSnapshotUrl": "https://web.archive.org/web/20070531101538/apify.com",
  "lastSnapshot": "2026-10-16T13:32:56+00:00",
  "ageYears": 19.4,
  "daysSinceLastSnapshot": 5,
  "monthsWithCaptures": 125,
  "yearsWithCaptures": 18,
  "activeYears": ["2007", "2008", "2015", "..."],
  "gapYears": ["2009", "2010"],
  "capturesByYear": { "2007": 3, "2008": 1, "2011": 3, "2025": 12 },
  "yearlySnapshotUrls": { "2007": "https://web.archive.org/web/2007.../apify.com" },
  "historyComplete": true
}
```

`capturesByYear` counts **months with at least one capture** of the homepage per year. If the Internet Archive's CDX API is temporarily overloaded, you still get first/last snapshot and age, and `historyComplete` is `false`.
Domains never archived get a free `never-archived` row.

### Pricing (pay per event)

- **$0.003 per domain with history** (`domain-history`) - $3 per 1,000 domains.
- Tiny start fee per run (`apify-actor-start`).
- Never-archived domains and errors are free. Use "Maximum cost per run" to cap spend.

### Notes

- "Age" = age of the first Wayback capture, a good proxy for website age (registration date can be checked with our Bulk Domain WHOIS / RDAP Actor).
- The Internet Archive is a non-profit; please keep concurrency low. Not affiliated with the Internet Archive.

# Actor input Schema

## `domains` (type: `array`):

Domains like example.com (URLs are reduced to the domain).

## `includeYearlySnapshots` (type: `boolean`):

One Wayback link per year with captures - quick visual history check.

## `onlySuccessfulCaptures` (type: `boolean`):

Ignore redirects / error pages when counting active months.

## `maxConcurrency` (type: `integer`):

Keep low - the Internet Archive rate-limits heavy use.

## Actor input object example

```json
{
  "domains": [
    "apify.com",
    "python.org",
    "stripe.com"
  ],
  "includeYearlySnapshots": true,
  "onlySuccessfulCaptures": true,
  "maxConcurrency": 3
}
```

# Actor output Schema

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

No description

## `runSummary` (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 = {
    "domains": [
        "apify.com",
        "python.org",
        "stripe.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("zhucl1006/wayback-domain-history-age-checker").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 = { "domains": [
        "apify.com",
        "python.org",
        "stripe.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("zhucl1006/wayback-domain-history-age-checker").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 '{
  "domains": [
    "apify.com",
    "python.org",
    "stripe.com"
  ]
}' |
apify call zhucl1006/wayback-domain-history-age-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,zhucl1006/wayback-domain-history-age-checker"
        }
    }
}
```

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/i89AOJPObpRYLJszH/builds/5zWoxxyV6RDd1jdoG/openapi.json
