Skip to main content

Util::Turnstile - recognition of Cloudflare Turnstile captchas

Parser Overview

This parser is used only as a connectable component in other parsers, where it may be necessary to solve Cloudflare Turnstile captchas, for example, in Ahrefs parsers, as well as in custom JavaScript parsers.

The principle of operation of this parser is to send Turnstile data (usually it is sitekey and the URL of the page where the Turnstile captcha was received) to the decryption service and receive a token in response, consisting of numbers and letters. The correctness of decryption depends only on the decryption service, usually the services almost always decrypt Turnstile correctly.

Capabilities

  • Supports working with such services: AntiCaptcha, RuCaptcha, 2captcha, CapMonster.cloud, CapSolver, captchas.io
  • Ability to adjust response waiting time and status check delay
  • Ability to solve captcha without using services. To enable this feature in the Provider, you need to select Auto (using Chrome). Chrome (puppeteer) is used for solving, take this into account when setting the number of threads.

Use Cases

  • Bypassing Cloudflare Turnstile in parsers, where it is optionally or necessarily necessary to solve this type of captcha to obtain results

Queries

The parser accepts two types of queries:

  • sitekey url
  • sitekey url proxy user-agent

The parameters are separated by a space and mean:

  • sitekey - the sitekey of Turnstile
  • url - the page where the Turnstile is located
  • proxy - the proxy through which Cloudflare Turnstile was obtained. The parameter should be in the format login:pass@ip:port@type for proxies with authentication or ip:port@type for proxies without authentication
    • type can be http, https, socks4, socks5
  • user-agent - the user agent with which the Turnstile was obtained

Output Result Options

  • $resp - response (token) of Cloudflare Turnstile
  • $error - if an error occurred, its description

Output of Cloudflare Turnstile Token

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.

ParameterDefault ValueDescription
Client keyClient key for online decryption services
Provider urlProvider URL, allows to override the domain. Multiple URLs can be specified separated by commas, the parser will use each of them in random order. Can be empty, the parser automatically uses the necessary one depending on the selected decryption service
ProviderAntiCaptchaDecryption service
Wait between get status5Delay between getting the status
Max wait time300Maximum decryption waiting time
Threshold % for Capmonster.Cloud0Confidence threshold (used only in capmonster.cloud)