> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/start-scanning/overview-scan-access-and-connectivity/captchas-impact.md).

# CAPTCHAs impact

How CAPTCHAs affect Snyk API & Web scans

A CAPTCHA, short for "Completely Automated Public Turing test to tell Computers and Humans Apart," is a challenge-response test used to confirm whether the user is human.

The primary goal of a CAPTCHA challenge is to ensure that a human initiates all actions taken on a website. CAPTCHAs typically accomplish this through letter and image recognition.

Implementing a CAPTCHA on a website helps protect against bots and spam. Snyk recommends a CAPTCHA for use in production.

## Helping Snyk API & Web bypass a CAPTCHA

When using Snyk, allow full access to the target you want to scan.

The crawler, an automated module that crawls the target and gathers endpoints and injection points for the scanner, cannot solve a CAPTCHA independently. As a result, a CAPTCHA can block the crawling of a target and hinder the scanning process.

To help Snyk bypass a CAPTCHA, you can:

* Disable the challenge on a target in a staging environment
* Allow Snyk outbound IP addresses to bypass the CAPTCHA in its settings

If these options do not work, add a cookie that disables the CAPTCHA when presented in a request, allowing Snyk to bypass it.

Implement the cookie on your target. The cookie checks whether the requests use the configured header, then disables the CAPTCHAs and gives clear access to the target.

Example cookie snippet:

```
if (isset($_COOKIE['disable_captcha']) && $_COOKIE['disable_captcha'] === 'aaaaaffff5557777777cccccc99812333ab') {}
```

{% hint style="warning" %}
Do not use the value of the cookie in this example. Generate your own secure value.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/start-scanning/overview-scan-access-and-connectivity/captchas-impact.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.