DataDome is an enterprise anti-bot and fraud-prevention vendor whose module runs at a site's edge, scoring requests in real time across network, device, and behavioral signals, and issuing a distinctive DataDome-branded challenge or block when a request scores as automated.
DataDome evaluates each request server-side against a machine-learning model trained on signals similar to other anti-bot vendors — IP reputation and ASN, TLS and browser fingerprint consistency, and behavioral patterns like navigation speed and mouse movement — and returns a decision in milliseconds, before the request reaches the origin server. A block typically shows as a 403 response, and a challenge routes through a distinctive CAPTCHA served from a captcha-delivery.com domain, which is a quick tell that a site runs DataDome specifically.
Like other enterprise anti-bot vendors, DataDome sets a first-party cookie (commonly named datadome) that tracks a session's trust score across requests — a missing or invalid cookie on subsequent requests is itself a signal the system checks.
DataDome is especially common on e-commerce, travel booking, classifieds, and ticketing sites, with particular strength in European markets. Its positioning overlaps directly with Akamai Bot Manager and Cloudflare Bot Management — three vendors competing for the same category of high-value, frequently-scraped sites — so a technique that works against one doesn't transfer automatically to the others.
As with any anti-bot vendor, the sustainable approach is presenting a coherent request identity across network, browser, and behavioral layers so the score never crosses the challenge threshold, rather than trying to solve the DataDome CAPTCHA after the fact.
How Crawlora handles this
Crawlora's request pipeline maintains that signal consistency automatically — matched fingerprints, appropriate IP type, realistic pacing — across whichever vendor a target runs, DataDome included, rather than needing a vendor-specific bypass maintained separately.
Glossary
FAQ
A challenge page served from a captcha-delivery.com domain, or a datadome cookie in the response, are the clearest tells. Response headers and block-page markup often reference DataDome directly as well.
No — they're competing products from separate companies, each with its own model and thresholds. DataDome has particular strength in European e-commerce and travel; a technique tuned for Cloudflare or Akamai doesn't reliably transfer to a DataDome-protected site.
Third-party solving services exist, but they add cost and latency per request, and treating the challenge as something to defeat after it appears is less durable than avoiding the score threshold that triggers it in the first place — DataDome updates its models continuously.
Beyond DataDome, Crawlora's own docs cover the rest of the stack — browse the APIs, test a request in Playground, and move from scraping infrastructure work to production data workflows.