JavaScript Detections
- A background script on HTML pages. A visitor that passes gets
cf_clearance. Send the URL and your proxy, get the cookie back. - Cloudflare JSD solver
Get a cf_clearance cookie without running a browser. notabot solves Cloudflare JavaScript Detections over plain HTTPS and charges only for solves that work.
They are separate products and a solver for one does not clear the others.
cf_clearance. Send the URL and your proxy, get the cookie back.cf_clearance.soon| What you see | Product | Use |
|---|---|---|
The page loads, and requests without cf_clearance are blocked | JavaScript Detections | cloudflare.jsd |
| A checkbox-style widget on a form | Turnstile | Not live yet |
| A “Just a moment” page before the content | Managed challenge | Not live yet |
Send the wrong type and the solver refuses instead of guessing, and you are not charged.
JavaScript Detections are the quiet check. Cloudflare injects a small script into HTML page views, the browser runs it, and the outcome is stored in a cf_clearance cookie. On its own that changes nothing. The site owner has to write a firewall rule that blocks or challenges requests whose detection did not pass, and they usually apply it to the pages and endpoints worth protecting rather than to the whole site.
Two consequences follow. The block often appears on a later request rather than the first one, because a new visitor has no result yet and owners are told not to enforce the rule on the first page. And the clearance does not last all day: Cloudflare gives the detection a 15-minute lifespan and re-injects the script before it runs out, so a long job should expect to solve again when the site starts challenging.
Source: Cloudflare, JavaScript Detections. More detail on the Cloudflare JSD solver page.
The cookies work with the user agent they came with, from the IP that earned them, on a client that looks like that browser.
user-agent header exactly.| Limit | Value | Note |
|---|---|---|
| Solve timeout | 30 seconds | Set your own client timeout to 60 seconds so it outlasts ours |
| Typical solve time | 2 to 10 seconds | Mostly round trips through your proxy. Our own work is well under a second |
| Requests per second | 50 per key, 200 per account | Over it you get rate_limited with a retry-after header |
| Proxy format | http://user:pass@host:port | SOCKS is not supported. Residential or mobile IPs clear far more often than datacenter ones |
Worked example in Node: Using the result. All limits: Limits.
A failed solve is never charged. The response names the reason, and each one has a specific fix.
| Reason | What it means | What to do |
|---|---|---|
CHALLENGE_NOT_FOUND | The page loaded but the protection script was not on it. The URL may not sit behind this solver's protection. | Check the URL is an HTML page behind JavaScript Detections. Turnstile and the managed challenge are different products. |
NOT_CHALLENGED | The site did not challenge this IP, so there was nothing to solve. Fetch the page directly. | Fetch the page directly. There was nothing to solve. |
GATE_NOT_CLEARED | The answer was valid but the site still held the session back. Nearly always a flagged IP. Retry on a fresh one. | Retry on a fresh residential or mobile IP. |
BLOCKED | The site refused the request before any challenge was shown. Usually the IP. | Change IP. Datacenter and already-flagged IPs cause most of these. |
domain_not_allowed | The domain is not approved for your account yet. | Request the site on the Sites page. |
Every code and reason: error reference.
€2.50 per 1,000 successful solves, and less as your lifetime top-ups grow. No subscription, credits never expire, and a solve that fails is not charged.
| Topped up in total | Level | You pay |
|---|---|---|
| Under €100 | List price | €2.50 |
| From €100 | −20% | €2.00 |
| From €250 | −30% | €1.75 |
| From €500 | −40% | €1.50 |
| From €1,000 | −50% | €1.25 |
| From €2,500 | −55% | €1.125 |
| From €5,000 | −60% | €1.00 |
| notabot API | Headless browser | |
|---|---|---|
| What you run | One HTTPS request | A Chrome instance per session, plus the servers under it |
| When the protection updates | We patch the solver. Your code is unchanged | You patch stealth plugins and redeploy |
| What you pay for | Successful solves only | CPU, memory and bandwidth, whether or not the page passes |
| Scaling up | Send more requests | Add more machines |
JavaScript Detections (JSD) is live and returns a cf_clearance cookie. Turnstile and the managed challenge are next.
If the page loads normally and a cf_clearance cookie appears after a background script runs, that is JavaScript Detections. A widget on a form that produces a token is Turnstile. A "Just a moment" page before the content is the managed challenge.
No. The solve is one HTTPS call. For your own requests to the site, use a client with a Chrome TLS fingerprint.
Yes. The clearance is tied to the IP that earned it, so pass the residential or mobile proxy you will send your own requests through.
€2.50 per 1,000 successful solves at list price, down to €1.00 at the top discount level. No subscription, credits never expire, and failed solves are free.
The solver refuses instead of guessing and returns solve_failed, which is not charged.
Page updated . Reference for every solver: documentation.
Login, copy a key, send one request. If the solve fails, it costs you nothing.