> For the complete documentation index, see [llms.txt](https://docs.vsat.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vsat.dev/understanding-datadome/dd-overview.md).

# What DataDome is

DataDome is a real-time bot-protection service that sits in front of a site as a CDN-edge gate. On every request it decides, from the IP's reputation, the TLS/HTTP fingerprint, the headers, and a JavaScript signal collected in the page, whether you are a browser it trusts.

You never talk to DataDome by name. You request the **target** (say `tickets.rolandgarros.com`); the response carries DataDome's verdict:

| response                                  | what it means                                                    |
| ----------------------------------------- | ---------------------------------------------------------------- |
| `200` + a `datadome` cookie, no challenge | trusted: you passed on reputation + signal                       |
| `403` with a small `dd={…}` stub          | challenged: you must solve to proceed                            |
| `403` / `t=bv` block page                 | hard-blocked: the exit's reputation is spent; solving won't help |

{% hint style="info" %}
️ The challenge you are served depends on your **trust level**, which is mostly your exit IP. A clean residential IP is often waved through; a datacenter IP is challenged; a burned IP is hard-blocked regardless of how perfect the payload is. Payload quality and exit quality are two independent gates.
{% endhint %}

This solver produces the **JavaScript signal** a real browser would have posted. It does not launder IPs: you bring the transport (proxy, TLS fingerprint, header order); the solver supplies the payload that makes a *trusted* exit stay trusted.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vsat.dev/understanding-datadome/dd-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.