CaptchaFox pitches itself as a privacy-first replacement for reCAPTCHA and hCaptcha. Sites can embed it inline, open it in a popup or keep it hidden, and its "OneClick" risk engine decides whether a visible challenge is needed at all. Most visitors see a simple click; suspicious sessions get an interactive task.
How to identifyLink to How to identify
- The script
https://cdn.captchafox.com/api.js - A
<div class="captchafox" data-sitekey="...">container - A hidden
cf-captcha-responseinput - A global
captchafoxobject withrender(),execute()andgetResponse() data-mode="inline|popup|hidden"anddata-start="none|auto|focus"attributes- Server-side validation at
https://api.captchafox.com/siteverify
ModesLink to Modes
- Inline: the widget sits inside the form
- Popup: the challenge opens in a modal window
- Hidden: nothing is shown and the site calls
captchafox.execute()when the form is sent - OneClick: risk-based, so many visitors never get an active challenge
How it worksLink to How it works
- The widget loads with its site key and asks for a challenge.
- A successful check writes a token into
cf-captcha-response. - The site's server sends that token and its secret to
api.captchafox.com/siteverify. - Each token works once and expires quickly.
- In hidden and OneClick modes, browser and behaviour signals decide whether the challenge can be skipped.
Free bypass methodsLink to Free bypass methods
| Method | What it does | Success Rate | Link |
|---|---|---|---|
| DrissionPage | Runs the widget in real Chromium and reads the token | 75-90% | g1879/DrissionPage |
| Patchright | Playwright with stealth patches | 70-90% | Kaliiiiiiiiii-Vinyzu/patchright-python |
| Camoufox | Firefox with anti-detect fingerprints | 70-90% | daijro/camoufox |
| undetected-chromedriver | Selenium with detection patches | 65-85% | ultrafunkamsterdam/undetected-chromedriver |
| ddddocr | OCR for the interactive image tasks | 60-80% | sml2h3/ddddocr |
Practical approachLink to Practical approach
- Start a stealth browser on a clean residential IP and open the page.
- Inline or popup mode: click the widget and wait for
cf-captcha-responseto fill. - Hidden mode: trigger
captchafox.execute()yourself (or let the site do it) and read the token it resolves. - If an interactive task appears, solve it with OCR or a vision model, or retry from a cleaner profile.
- Send the form without delay, because tokens are short-lived and single-use.
Practical tipsLink to Practical tips
- Hidden and OneClick modes mostly judge the fingerprint and the IP. Fresh datacenter addresses draw far more challenges.
- Use the same session and User-Agent from the challenge through to the submission.
- Reloading the widget after it has passed can void the token.
- With
data-start="auto"the widget may pass on its own. Give it a moment before clicking anything. captchafox.getResponse()is a steadier way to grab the token than polling the DOM.