Wayback Machine History: Site Age, Snapshots & Archived URLs avatar

Wayback Machine History: Site Age, Snapshots & Archived URLs

Pricing

Pay per event

Go to Apify Store
Wayback Machine History: Site Age, Snapshots & Archived URLs

Wayback Machine History: Site Age, Snapshots & Archived URLs

Use the Internet Archive's official CDX API to get a site's first and last archive date. No login. Export JSON/CSV/Excel. Pay only per result.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Jeremy Yarbrough

Jeremy Yarbrough

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

15 days ago

Last modified

Share

Use the Internet Archive's official CDX API to get a site's first and last archive date, with no login, no browser and no code. Export to JSON, CSV or Excel, or use the API.

Use the Internet Archive's official CDX API to get a site's first and last archive date, age and yearly activity, every distinct snapshot of a page (changes only), or all archived URLs under a domain (find old/deleted pages for SEO recovery).

Use cases

  • Verify how old a business or domain really is
  • Recover deleted pages and old URLs for SEO redirects
  • See every change to a competitor's pricing page

Input

FieldTypeNotes
targetsarrayDomains or page URLs, e.g. example.com or example.com/pricing.
modestringsummary = one row per target (age, first/last capture, activity); snapshots = capture list of a page; urls = all distinct archived URLs under a domain.
matchTypestringexact page, prefix (path and below), host, or domain (incl. subdomains). 'urls' mode uses domain when exact.
fromstringYYYY-MM-DD (optional).
tostringYYYY-MM-DD (optional).
collapsestringsnapshots mode: digest = only when content changed; timestamp:8 = one per day; timestamp:6 = one per month; none.
statusFilterstringOnly captures with this status (blank = all).
mimeFilterstringe.g. text/html or application/pdf (blank = all).
maxRowsPerTargetintegerCap for snapshots/urls modes.
maxConcurrencyintegerKeep low; the Archive is a nonprofit.

Example input

{
"targets": [
"apify.com",
"therealtour360.com"
],
"mode": "summary"
}

Output

One dataset item per result. Main columns: type, target, firstSnapshot, lastSnapshot, siteAgeYears, originalUrl, capturedAt, statusCode, mimeType, archiveUrl, error. A RUN_SUMMARY record is saved to the default key-value store. See the sample output in the Output tab.

Pricing

Pay per result, with no monthly rental or subscription:

  • Target summary: $0.003
  • Snapshot or URL row: $0.0003

Example: 1,000 results cost about $3.00 in fees. Apify's free plan includes $5 of monthly credit, which is enough to test this Actor.

FAQ

Do I need an account, cookies or a login for the source site? No. Wayback Machine History uses public data sources only, so there is nothing to connect and no account to risk.

How much will a run cost? You pay only for results delivered (see Pricing above), plus Apify platform usage, which the free plan's monthly credit easily covers for test runs. Start with a small limit to see the exact cost per run.

Can I export to CSV, Excel or Google Sheets? Yes. Every run's dataset can be downloaded as JSON, CSV, Excel, XML or HTML, or pushed to Google Sheets, Make, Zapier, n8n, Slack or a webhook through Apify integrations.

Can I run it on a schedule or from my own code? Yes. Add an Apify Schedule (hourly, daily, weekly) or call it through the Apify API / Python & JavaScript clients. It also works with AI agents through the Apify MCP server.

What happens if an input is invalid or a source is down? The run keeps going. The bad input gets a row with an error field so you can see what failed, and you are not charged for results that were not delivered.

Is this legal to use? It collects publicly available data. You are responsible for using the output in line with the source's terms and privacy laws such as GDPR/CCPA; don't use it for spam.

Something missing or broken? Open an issue on the Issues tab. Feature requests are usually added within a few days.

Scheduling / monitoring

Create a Schedule (daily/weekly) and connect a webhook or Slack/email integration.

Fair use

Official public APIs only, no login. Do not use output for spam or harassment. Respect the data sources' rate limits and terms.