Skip to main content

DataDome slider captcha

Challenge/DataDome

Also known as DataDome captcha, DataDome slider

The DataDome slider captcha is a challenge that DataDome serves on a 403 block page. The challenge itself is loaded from geo.captcha-delivery.com under the /captcha/ path. Once it is solved, DataDome issues a new datadome cookie and the blocked request can be retried.

How to recognize it

How to recognize it
Status code
403 with a small HTML block page containing a dd object
Script
ct.captcha-delivery.com/c.js (slider); i.js means interstitial
dd object
'rt':'c' for slider; 'rt':'i' for interstitial
URL pattern
geo.captcha-delivery.com/captcha/
API response
From JSON/XHR endpoints: a JSON body whose url points to geo.captcha-delivery.com/captcha/
Hard block
't':'bv' in the dd object: the IP is blocked and solving the slider has no effect

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:

  1. Status code. A 403 on a page load, or a JSON body with a url to captcha-delivery.com on an API call.
  2. The dd object. The HTML contains a small script that sets var dd={...}. The rt field decides the challenge: 'rt':'c' is the slider (captcha), 'rt':'i' is the interstitial.
  3. The script at the bottom. The slider block page loads ct.captcha-delivery.com/c.js. The interstitial loads i.js from the same host.
  4. 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.
  5. 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.
  6. The cookie. The 403 response also sets a datadome cookie. 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.js versus i.js on 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 .jpg puzzle and the .frag.png piece;
  • 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.

Questions

What is the DataDome slider captcha?

It is the puzzle challenge DataDome serves on its 403 block page when it does not trust a request. A piece has to be dragged into a gap in an image. A correct solve returns a new datadome cookie, after which the blocked request can be retried.

How do I tell the DataDome slider from the interstitial?

Look at the block page. The slider has 'rt':'c' in the dd object and loads c.js from ct.captcha-delivery.com. The interstitial has 'rt':'i' and loads i.js. The challenge URLs differ too: /captcha/ for the slider, /interstitial/ for the interstitial.

Is geo.captcha-delivery.com the slider captcha?

Not on its own. geo.captcha-delivery.com is DataDome's challenge host. It serves the slider under /captcha/ and the interstitial under /interstitial/, so the path tells you which challenge you are facing.

What does 't':'bv' mean on a DataDome block page?

It means the IP address is hard-blocked. Solving the slider has no effect in that case; the request needs a different IP.

Why does the slider come back after I solve it?

Usually because the new datadome cookie from the JSON check response was not stored, or because the session itself looks automated: a non-Chrome TLS fingerprint, inconsistent client hints, a wrong header order or a flagged IP.

Further reading

Technical review: Hyper Solutions engineering, Nov 18, 2026