Getting started
This page explains the flow of solving both the interstitial and slider challenge of DataDome.
If you already familiar with solving DataDome challenges, you can either install one of our SDKs for easy integration, or head over to our API Reference if you want to handle the implementation yourself.
Interstitial
This challenge is served using a 403 status code and a response body that looks as follows:
<html>
<head>
<title>example.com</title>
<style>#cmsg{animation: A 1.5s;}@keyframes A{0%{opacity:0;}99%{opacity:0;}100%{opacity:1;}}</style>
</head>
<body style="margin:0">
<p id="cmsg">Please enable JS and disable any ad blocker</p>
<script data-cfasync="false">var dd={'rt':'i','cid':'AHrlqAAAAAMACAOLE2sBBRMATaDxmw==','hsh':'13C44BAB3C9D728ABD66E2A9F0233C','b':1501854,'s':48047,'host':'geo.captcha-delivery.com'}</script><script data-cfasync="false" src="https://ct.captcha-delivery.com/i.js"></script>
</body>
</html>
This is almost the same response you would receive with a Slider challenge, however the reference to this URL: https://ct.captcha-delivery.com/i.js
is unique to interstitial.
Parsing the HTML
Before we explain how you can manually parse the required values from the HTML posted above, first are shown code snippets of how it can be done easily with our SDKs:
// reader is an `io.Reader` which holds the response body of the HTML.
// datadomeCookie is the cookie value of the cookie with name "datadome",
// this cookie is set by the 403 block page.
// referer is the URL that served the 403 block page.
deviceLink, err := datadome.ParseInterstitialDeviceCheckLink(reader, datadomeCookie, referer)
if err != nil {
// Handle the error
}
// deviceLink will look like: https://geo.captcha-delivery.com/interstitial/?...
If you would rather parse the response yourself, you will need to extract the following fields from the dd
object that can be found in the response body: cid
, hsh
, s
, b
.
You also need to store the URL that received the block, it is used as the referer
, and the datadome
cookie that is set on this blocked request.
You can now build the URL as follows:
https://geo.captcha-delivery.com/interstitial/?initialCid={cid}&hash={hsh}&cid={datadomeCookie}&referer={referer}&s={s}&b={b}&dm=cd
We will call this URL the deviceLink from now on.
Fetching the interstitial script
After having parsed the deviceLink in the previous step, you need to make a GET request to it. Make sure that you are sending the same headers and in the same order as your browser. Read and save the response body of this request as we need it to submit to the Hyper Solutions API.
Fetching the payload from API
Again we have handy SDK functions to help you with these API calls, if you want to implement the API calls yourself, head over to the API Reference. There are 3 values that you need for these API calls:
userAgent: Your browser's User-Agent.
deviceLink: The link we have parsed in one of the previous sections.
html: The full response contents of the GET request you made to the deviceLink URL.
You can then generate the payload with the SDK as follows:
payload, err := session.GenerateDataDomeInterstitial(ctx, &hyper.DataDomeInterstitialInput{
// Set the required input fields: userAgent, deviceLink, html
})
if err != nil {
// Handle the error
}
Posting payload, solving challenge
The payload returned by the HyperSolutions API in the previous step is an already concatenated Form Data string, you can POST this to the following URL:
https://geo.captcha-delivery.com/interstitial/
And make sure you are matching the headers in the order that your browser used. The response of this POST request will be as follows:
{
"cookie": "datadome=cookievalue; Max-Age=31536000; Domain=.example.com; Path=/; Secure; SameSite=Lax",
"view": "redirect",
"url": "https://www.example.com/path"
}
You can parse the JSON response, and update your cookieJar with the "cookie"
you received from DataDome.
You have now successfully solved DataDome's interstitial challenge, retrying the request that served this block should not give you a challenge anymore.
Slider
This challenge is served using a 403 status code and a response body that looks as follows:
<html>
<head>
<title>example.com</title>
<style>#cmsg{animation: A 1.5s;}@keyframes A{0%{opacity:0;}99%{opacity:0;}100%{opacity:1;}}</style>
</head>
<body style="margin:0">
<p id="cmsg">Please enable JS and disable any ad blocker</p>
<script data-cfasync="false">var dd={'rt':'c','cid':'AHrlqAAAAAMA6gifcHcCX3IATaDxmw==','hsh':'EC3A9FB6F2A31D3AF16C270E6531D2','t':'fe','s':43337,'e':'5e8c40553ff322bdcba3d8e59224b6a2858cf1080c5e0f3923cc0fcd3d4217d5','host':'geo.captcha-delivery.com'}</script><script data-cfasync="false" src="https://ct.captcha-delivery.com/c.js"></script>
</body>
</html>
If in the response, t
is set to bv
, it means your proxy is hard blocked, solving the challenge will not have any effect.
This is almost the same response you would receive with a Interstitial challenge, however the reference to this URL: https://ct.captcha-delivery.com/c.js
is unique to slider.
Parsing the HTML
Before we explain how you can manually parse the required values from the HTML posted above, first are shown code snippets of how it can be done easily with our SDKs:
// reader is an `io.Reader` which holds the response body of the HTML.
// datadomeCookie is the cookie value of the cookie with name "datadome",
// this cookie is set by the 403 block page.
// referer is the URL that served the 403 block page.
deviceLink, err := datadome.ParseSliderDeviceCheckLink(reader, datadomeCookie, referer)
if err != nil {
// Handle the error
}
// deviceLink will look like: https://geo.captcha-delivery.com/captcha/?...
If you would rather parse the response yourself, you will need to extract the following fields from the dd
object that can be found in the response body: cid
, hsh
, t
, s
, e
.
You also need to store the URL that received the block, it is used as the referer
, and the datadome
cookie that is set on this blocked request.
You can now build the URL as follows:
https://geo.captcha-delivery.com/captcha/?initialCid={cid}&hash={hsh}&cid={datadomeCookie}&t={t}&referer={referer}&s={s}&e={e}&dm=cd
Fetching the slider script
After having parsed the deviceLink in the previous step, you need to make a GET request to it. Make sure that you are sending the same headers and in the same order as your browser. Read and save the response body of this request as we need it to submit to the Hyper Solutions API.
Fetching the slider puzzle
In order for the Hyper Solutions API to solve the slider challenge, it needs access to the images involved. The HTML that we have retrieved in the previous step contains links like these:
<link rel="preload" href="https://dd.prod.captcha-delivery.com/image/2024-07-20/82c36751e42b098407a4720cb9637462.jpg" as="image" crossorigin="anonymous">
<link rel="preload" href="https://dd.prod.captcha-delivery.com/image/2024-07-20/82c36751e42b098407a4720cb9637462.frag.png" as="image" crossorigin="anonymous">
It is up to you how you want to parse it, however here are two regex expressions that you can use:
(https:\/\/dd\.prod\.captcha-delivery\.com\/image\/.*?\.jpg)
(https:\/\/dd\.prod\.captcha-delivery\.com\/image\/.*?\.frag.png)
You need to make a GET request to both links and store both responses (base64 encoded) as the puzzle
for the jpg and as piece
for the png.
Fetching the payload from API
Again we have handy SDK functions to help you with these API calls, if you want to implement the API calls yourself, head over to the API Reference. There are 5 values that you need for these API calls:
userAgent: Your browser's User-Agent.
deviceLink: The link we have parsed in one of the previous sections.
html: The full response contents of the GET request you made to the deviceLink URL.
puzzle: The base64 encoded response bytes from the jpg image.
piece: The base64 encoded response bytes from the
.frag.png
image.
You can then generate the payload with the SDK as follows:
checkUrl, err := session.GenerateDataDomeSlider(ctx, &hyper.DataDomeSliderInput{
// Set the required input fields
})
if err != nil {
// Handle the error
}
// Create a GET request to the checkUrl
Posting payload, solving challenge
Our API returns a simple URL as the result of solving the slider challenge, all that is required is to make a GET request to this URL which looks as follows:
https://geo.captcha-delivery.com/captcha/check?cid=...
The response of this GET request will be as follows:
{
"cookie": "datadome=cookievalue; Max-Age=31536000; Domain=.example.com; Path=/; Secure; SameSite=Lax"
}
You can parse the JSON response, and update your cookieJar with the "cookie"
you received from DataDome.
You have now successfully solved DataDome's slider challenge, retrying the request that served this block should not give you a challenge anymore.
Last updated