When DataDome shows the slider captcha
DataDome scores every request to a protected site, and the DataDome slider captcha is one of the two ways it pushes back. When it decides not to serve the page, it answers with a 403 and a small HTML block page instead. That block page carries one of two challenges: the interstitial, a device check that runs without any user input, or the slider, a puzzle in which a piece has to be dragged into a gap in an image.
API calls can get the slider too. Instead of the HTML block page, a JSON or XHR request may come back with a JSON body whose url field points at geo.captcha-delivery.com/captcha/. An interstitial can also hand over to the slider. Its solve response then says view: captcha and includes a slider URL.
How to recognize the DataDome slider captcha
Work through the block page in this order:
- Status code. A 403 on a page load, or a JSON body with a
urlto captcha-delivery.com on an API call. - The dd object. The HTML contains a small script that sets
var dd={...}. Thertfield decides the challenge:'rt':'c'is the slider (captcha),'rt':'i'is the interstitial. - The script at the bottom. The slider block page loads
ct.captcha-delivery.com/c.js. The interstitial loadsi.jsfrom the same host. - The path. The slider itself is served under
geo.captcha-delivery.com/captcha/. The interstitial uses/interstitial/on the same host, so the domain alone does not tell you which challenge you have. - Hard block. If the dd object has
't':'bv', your IP address is blocked outright. Solving the slider will not change anything; change the proxy instead. - The cookie. The 403 response also sets a
datadomecookie. Its value is part of the challenge link, so keep it.
Slider or interstitial?
Both challenges arrive on the same kind of block page, and both end with a new datadome cookie. The differences:
- User interaction: the slider expects a drag; the interstitial needs none.
- dd object:
'rt':'c'for the slider,'rt':'i'for the interstitial. - Script:
c.jsversusi.json ct.captcha-delivery.com. - Challenge path:
/captcha/versus/interstitial/on geo.captcha-delivery.com. - What the solver needs: the slider also needs the puzzle image (
.jpg) and the piece (.frag.png), both loaded from dd.prod.captcha-delivery.com.
DataDome markets its invisible check as Device Check; in Hyper Solutions' docs the same challenge is called the interstitial.
What a slider looks like in a capture
If you record the traffic in a HAR file, the slider shows up as a short, recognizable sequence:
- the 403 block page on the site's own domain;
- a GET to
geo.captcha-delivery.com/captcha/?initialCid=..., the challenge page; - a GET to a versioned challenge bundle on ct.captcha-delivery.com;
- two image requests to dd.prod.captcha-delivery.com, the
.jpgpuzzle and the.frag.pngpiece; - a GET to
geo.captcha-delivery.com/captcha/check, which answers with JSON containing the new cookie.
After the slider is solved
The check response is JSON with a cookie field. That new datadome value does not arrive as a normal Set-Cookie on your original request, so update your cookie jar yourself and then retry the request that was blocked.
If the retry is blocked again straight away, look at the session rather than the solve: a TLS fingerprint that does not match Chrome, missing or inconsistent client hints, a header order no browser sends, or a proxy IP that DataDome has already flagged.
The full solving flow is in the DataDome slider docs. The Hyper Solutions DataDome API solves both the slider and the interstitial. Each challenge has its own endpoint, and one call solves one challenge.