Lead List Website Check: dead, parked, hijacked, bot-walled avatar

Lead List Website Check: dead, parked, hijacked, bot-walled

Pricing

$2.00 / 1,000 site checkeds

Go to Apify Store
Lead List Website Check: dead, parked, hijacked, bot-walled

Lead List Website Check: dead, parked, hijacked, bot-walled

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

Pricing

$2.00 / 1,000 site checkeds

Rating

0.0

(0)

Developer

OMENZ

OMENZ

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

15 days ago

Last modified

Features

Limited permissions

Share

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

next_action: what your pipeline should do next, so it doesn't pay for a wasted step:

  • proceed: go ahead
  • use_variant: this URL fails, but working_variant works (www vs no-www, http vs https)
  • needs_browser: real site, but its content only loads with JavaScript
  • retry_once: timeout or server error; try once more later
  • wait: the site is rate-limiting; slow down
  • stop: dead, broken certificate, or bot protection; don't spend more on it
  • skip: parked, for sale, hijacked, or not the business anymore

status is one of:

  • live: the site answers and looks like a real site
  • parked: for sale / parked / suspended / "reserved" holding page / JavaScript parking lander / a page showing only the domain name
  • hijacked_spam: the domain now serves spam (we keep finding local-business domains taken over by gambling and piracy sites)
  • 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)
  • tls_error: the HTTPS certificate is broken (the reason is in notes)
  • rate_limited, http_error, dead (no DNS / redirects to a host that doesn't exist / no response / 404), invalid_url

Plus:

  • working_variant: a working version of the address when the one you gave fails
  • moved_to: the business moved to its own new domain (still live)
  • js_only: the page has almost no readable text without JavaScript
  • placeholder_name: a site-builder placeholder left in the site's own name data (e.g. "Your Site Title")
  • final_url, http_status, title, notes

Input

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

or with names:

{ "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?

Every version is tested on a frozen holdout of sites it had never seen: graded by hand, rules fixed before the run, no changes after. This version's test was 40 sites (20 real businesses + 20 generic domains picked blind):

  • usable vs not usable: 40 of 40
  • exact status: 40 of 40
  • sensible next_action: 40 of 40
  • real businesses wrongly called parked: 0

The previous holdout scored 38 of 39 on the same criteria. Across our tests it has caught local-business domains hijacked by gambling spam and a pirate sports-streaming site, JavaScript parking landers, for-sale domains, broken certificates, and Cloudflare-walled sites. A business-name match was tested too and dropped: listing names ("... House of Chicken 'N Waffles") too often differ from the site's own wording.

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.
  • Bot protection can change from day to day; a site that answered yesterday may be blocked_by_bot_protection today.
  • tls_error is what a strict automated client gets. Some browsers still load sites with an incomplete certificate chain.
  • No phone numbers or other contact data are returned. Public pages only, usually 1-2 requests per site (up to ~6 when the given address fails and variants are tried), no AI calls.

Coming back? Tell us what to add

If this runs in your pipeline or agent regularly, thank you. You're exactly who we build for. Open an issue on the Issues tab (https://apify.com/omenz/lead-list-website-check/issues) with:

  • what you use it for (lead lists, enrichment, outreach, agents...)
  • the next check you'd want in the same call, so your workflow makes one stop instead of several
  • anything it labels wrong

We read every one, and repeat users' requests go to the front of the line.

Built by OMENZ: https://omenz.org

More OMENZ tools

  • Agent-Ready Checker: is a business website ready for AI assistants and agents? Score + fixes
  • Changed?: did a page really change since the agent's last visit, or just its timestamp?

OMENZ builds tools, research and stories for the agentic internet: omenz.org