Util::Turnstile - Cloudflare Turnstile captcha recognition
Overview of the parser
This parser is used only as a plug-in component in other parsers where it may be necessary to solve Cloudflare Turnstile captchas, for example, Ahrefs parsers, as well as custom JavaScript parsers.
The principle of this parser's operation consists of sending Turnstile data (usually the sitekey and the url of the page where the Turnstile captcha was received) to a solving service and receiving a token in response, consisting of numbers and letters. The correctness of the solving depends only on the solving service; as a rule, services almost always solve Turnstile correctly.
Capabilities
- Support for working with these services: AntiCaptcha, RuCaptcha, 2captcha, CapMonster.cloud, CapSolver, captchas.io
- Ability to configure response wait time and status check delay
- Ability to solve captchas without using services. To enable this feature, select
Auto (using browser)in Provider. A browser is used for solving; keep this in mind when configuring the number of threads.
Use cases
- Bypassing Cloudflare Turnstile in parsers where it is optionally or mandatory to solve this type of captcha to obtain results
Queries
The parser accepts two types of queries:
sitekeyurlsitekeyurlproxyuser-agent
Parameters are separated by a space and mean:
sitekey- this is the Turnstile sitekeyurl- the page where the Turnstile is locatedproxy- the proxy through which the Cloudflare Turnstile was received. The parameter must be in the formatlogin:pass@ip:port@typefor proxies with authorization orip:port@typefor proxies without authorization- type can be
http,https,socks4,socks5
- type can be
user-agent- the user agent with which the Turnstile was received
Output results examples
$resp- Cloudflare Turnstile response (token)$error- if an error occurred, its description
Cloudflare Turnstile token output
Result format:
$resp
Result example:
0.uM0rQLy_vdWZNwOml8TMpvPgtXuqMs3H_2A7D5txxc27kHNFcGh2UOS1MQ82GiF3Dd6-VyOEgdBf1Ef3Q6xjwRYZH3V8YJdv4wgxfTtyH5stVsBOP6qWrE0Zu-txfDmJIJ_THkeK8wrYODLwj3p948zdiufJScERCVhsx1aPIurXAidPWhJslVutd4uTbMAvuGcYg7Nj-wwbW6VKGuofBHIx116Xt7_9eXISzWFy5se95e2FYVY4n4oGU3xSkoUnUCw0fcBMBP8Vik8Qde-qd53mc7YAGKeRKj9yV0t2erTc4i9ZeRjR22Fxm1nN_SkbdAHjj-oATJmxyfMAFoT_MEwe2WliuvuoPrkCAZYe8S0.QqD0sL8h2B_8jYaa792YPA.04643a6fbd94c593eee9770924ddefbd6d227e84dcfca973ab840728c122fc5d
Possible settings
The Provider parameter is used to select the service.
| Parameter | Default value | Description |
|---|---|---|
| Client key | Client key for online solving services | |
| Provider url | Provider URL, allows overriding the domain. Multiple can be specified separated by commas; the parser will use each of them in random order. Can be empty; the parser automatically uses the required one depending on the selected solving service | |
| Provider | AntiCaptcha | Solving service |
| Wait between get status | 5 | Delay between status checks |
| Max wait time | 300 | Maximum solving wait time |
| Max browser pages for Auto mode | Limits the number of simultaneously open browser pages when solving captchas if Auto (using browser) is selected in Provider |