Util::ReCaptcha3 - Google ReCaptcha v3 recognition
Overview of the parser
This parser is designed to be used as a pluggable component in other parsers where it may be necessary to solve Google ReCaptcha v3.
The principle of this parser's operation is to send ReCaptcha data (this is always the sitekey and the URL of the page where the ReCaptcha was received) to a solving service and receive a token consisting of numbers and letters in response. The correctness of the solving depends only on the solving service; as a rule, services almost always solve ReCaptchas correctly.
Capabilities
- Supported services: AntiCaptcha, RuCaptcha, 2captcha, XEvil, CapMonster, CapMonster.cloud, CapSolver, captchas.io, NextCaptcha
- Ability to configure response timeout and status check delay
Use cases
- Recognition of Google ReCaptcha v3 in built-in parsers where solving captchas is optionally or mandatory required to obtain results
- Recognition of Google ReCaptcha v3 in custom JS parsers
Queries
The parser accepts queries in the following format:
sitekeyurl
Parameters are separated by a space and mean:
sitekey- this is the ReCaptcha sitekey, in some services it is called websitekey. As a rule, the sitekey needs to be obtained from the page code and is usually located in the URL of the connected script:
https://www.google.com/recaptcha/api.js?render=SITEKEY
Also, the sitekey in the page code can be specified as a function argument:
grecaptcha.execute(SITEKEY, {action:'verify'}).
url- the page where the ReCaptcha is located
Output results examples
$resp- ReCaptcha response$error- if an error occurred, its description
ReCaptcha token output
Result format:
$resp
Result example:
03AGdBq24qfVWiRMofkMHuxaaW024vkt2Oc4Nnt4WXs3PdV0fJlpDystp444u_rG8HvuJUgN3n-upnHJXeQODxHjn_X9JdRlKEzhDnatYyehxN00WDWN_37LKwdHOgER2TrdB7XBKqrz5rko_CGWea6R1Lfe3eKmkoOeHkTyn8H3ZI90wcSvZR8gSztvq5EZWpGdNgLq15w84F92-PR8S051gUH2Ls82An0N4iiAIcTFrOTQZizqfIjgVzCzqHhSaigIPGy6j8-3nt1sac7q6Xn26fKLsQzd4hZDmrlem5rNoK-IQHEb_AUJ6r4UxQZQ-z4hk9wPpzdeiCi81sxWEX5YI-cn4cWYFsoWutv_DYvZy87Iog7u1VELGWvjT3XwkY3MyDZzpUfauyCGSd5oouLDhV5YnRPfMm-gWQUSRpt28z5xbVbwGSAfmMLEpFboCgKZdUhb-IdAiKHGA4oSXB3RhOA9TQZR-ETVqyUG8A4wJEXdCvEHU7Uhw
Possible settings
The Provider parameter is used to select the service to be used.
For online services (AntiCaptcha, RuCaptcha, 2captcha, CapMonster.cloud, CapSolver, captchas.io), the Client key parameter must be set.
| Parameter | Default value | Description |
|---|---|---|
| Client key | Client key for online solving services | |
| Provider url | Provider URL, allows overriding 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 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 |
| minScore | 0.3 | Minimum confidence score for the result. Selected experimentally for each individual site. When contacting the solving service, it defines a filter to select a worker with the required minimum score |
| pageAction | The value of the action parameter passed to Google, which the site owner then sees when verifying the token. Usually specified as a function argument: grecaptcha.execute('sitekey', {action:'ACTION VALUE'}) | |
| isEnterprise | ☐ | Tells the solving service to solve this ReCaptcha as Recaptcha Enterprise V3. Does not work in all solving services |