Cloudflare Bypasser - Fetch HTML Behind Protection avatar

Cloudflare Bypasser - Fetch HTML Behind Protection

Pricing

from $30.00 / 1,000 page bypasseds

Go to Apify Store
Cloudflare Bypasser - Fetch HTML Behind Protection

Cloudflare Bypasser - Fetch HTML Behind Protection

Bypass Cloudflare challenges and fetch clean HTML from any protected page. Residential proxies, sticky sessions and a headless browser fallback. Pay only for successfully fetched pages.

Pricing

from $30.00 / 1,000 page bypasseds

Rating

0.0

(0)

Developer

Long Li

Long Li

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 hours ago

Last modified

Share

Cloudflare Bypasser Lite — Fetch HTML from Any Protected Page

Give it a URL behind a Cloudflare challenge ("Just a moment...", "Checking your browser", managed challenges) and get the real page HTML back as structured data — no proxies to buy, no headless browsers to babysit, no captchas to solve manually.

Built for developers, AI agents and data pipelines that need to read pages, not admire error pages.

How it works — a 3-layer ladder, battle-tested on hard targets

  1. HTTP with residential sticky sessions — browser-grade TLS fingerprinting, navigation-complete request headers (sec-fetch-*) and a cookie jar that keeps Cloudflare clearance cookies between attempts.
  2. Session alternation — sticky exit IP and fresh residential IP alternate across retries, because some residential ranges are pre-flagged and rotation is the escape hatch.
  3. Headless Chromium fallback — when plain HTTP keeps hitting the challenge, the page runs in a real browser through the same residential proxy with automation flags disabled (navigator.webdriver scrubbed), executing the JS challenge and returning the cleared page.

You pay only for successfully fetched pages — failed URLs are returned with a clear error reason and cost nothing.

Input

FieldDescription
URLs to fetchAny page URLs. Works on plain pages too.
Proxy configurationResidential proxy recommended (auto-detected when empty). Datacenter IPs are usually blocked outright.
HTTP retries per URLAttempts before the browser fallback (default 3).
Headless browser fallbackOn by default — the layer that gets the hardest pages.
Challenge wait (ms)How long the browser waits for an interstitial to clear (default 25 s).
Truncate HTML to N charactersKeep datasets small when you only need a sample.
Save response headersInclude final response headers in the output.
Max concurrent URLsParallel fetches (default 5).

Output

One dataset item per URL:

FieldDescription
okTrue when real page HTML was fetched (2xx, not an interstitial).
htmlFull page HTML (optionally truncated).
httpStatusFinal HTTP status code.
fetchMethodhttp (sticky residential sessions) or browser (Chromium fallback).
challengeEncounteredWhether a Cloudflare challenge was detected on the way.
durationMsTotal time spent on the URL.
errorFailure reason when ok is false.
finalUrl / headersAfter-redirect URL and response headers (optional).

Use it as an API

# Run the actor and get the dataset items
curl -X POST "https://api.apify.com/v2/acts/liver0914~cloudflare-bypasser-lite/runs?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"startUrls": [{"url": "https://example-protected-site.com"}]}'

Typical flow for pipelines: run it, read the dataset, feed html into your parser — or point Contact Info Scraper Lite at the fetched pages to mine emails and social links.

FAQ

Does it solve every Cloudflare site? No tool honestly can. It reliably passes interstitial/JS challenges (the "Just a moment..." pages) — the overwhelming majority of protected sites. Pages requiring login, interactive captcha solving, or per-request turnstile clicks are out of scope, and those URLs come back with ok: false and a precise reason — at zero cost.

Do I need my own proxies? No. It uses Apify residential proxies automatically when you leave the proxy field empty. You can also plug in custom proxy URLs.

What about non-Cloudflare protections (Akamai, PerimeterX, DataDome)? The HTTP layer often passes lighter WAFs, but the browser fallback is tuned for Cloudflare. For other WAFs treat it as best-effort.

Is there a rate limit? Concurrency is capped by your plan. Sequential retries are built in; hammering a single domain with hundreds of parallel URLs is neither supported nor polite.

Will I pay for failed pages? No. Charging happens per successfully fetched page (page-bypassed event).

Pricing

Pay-per-event: you are charged for each successfully fetched page, plus Apify platform usage for compute and residential proxy traffic. Runs while the actor is on the free plan cost platform usage only.