ScrapingProxies

DataDome 403: Same Status, Different Outcomes (Scraping)

JS
Founder
Published
August 10, 2026
Updated
August 30, 2026
Read Time
6 min read
Same 403 envelope for device check, puzzle, and hard block

If your Python logs are a wall of HTTP 403 with almost no logo, you may be staring at DataDome — and the status code is lying about severity. Device Check, CAPTCHA, and ban routinely share the same envelope. Teams either rotate residential exits forever or, worse, parse a JSON challenge as if it were API data.

Full classification recipes live in Handle DataDome blocks in Python. This post is the error-string entry point: what to search for when the only thing in your logs is a bare 403.

Engineers paste x-datadome: protected into Google because the HTML never says “DataDome.” Titles are often just the registrable domain (leboncoin.fr, g2.com). The visible sentence Please enable JS and disable any ad blocker is deliberately misleading — you are not running an ad blocker; you are missing a JS runtime the edge expects. Until you learn the header and cookie names, every 403 looks identical to a generic WAF deny or a Cloudflare sibling.

That ambiguity is the product design. Your job is to name the vendor, then name the layer, then spend money only on the layer that failed.

Name the vendor, then the layer, then spend
Name the vendor from header and cookie names, then the layer, then spend. A generic WAF is not this.

Trust markers, not vibes

SignalNotes
x-datadome: protectedLiteral value protected — strongest client-visible header
Set-Cookie: datadome=…Long-lived Secure cookie; typically not HttpOnly so the JS tag can read it
js.datadome.co/tags.jsScript host to expect (not a tags.datadome.co folklore host)
captcha-delivery.comChallenge / CAPTCHA delivery domain in body or JSON url
Body textPlease enable JS and disable any ad blocker on HTML variants

Optional companions seen on challenges: x-datadome-cid, x-dd-b (treat presence only — do not invent severity from the integer), and access-control-expose-headers: x-dd-b, x-set-cookie.

CDN misdirection is common: DataDome can sit behind Cloudflare or CloudFront. Attribute the vendor from DataDome markers, not Server: cloudflare.

x-datadome protected plus the datadome cookie
x-datadome: protected and the datadome cookie are the markers. Server: cloudflare is not the vendor.

Same 403, three jobs

With JavaScript disabled, outcomes collapse to a tiny HTML page. With JS on, humans see:

  1. Device Check / interstitial — brief verification; a real browser often clears it silently
  2. CAPTCHA — slider/puzzle via captcha-delivery
  3. Hard block — no useful challenge path for that identity

Your HTTP client sees 403 for all three. Branch on body shape:

Check, puzzle, hard block — your client sees 403 for all
Check, puzzle, and hard block share one 403. Branch on body shape.
Code Snippet
import json
from urllib.parse import urlparse, parse_qs

def classify_datadome_body(resp):
    text = (resp.text or "").strip()
    if text.startswith("{"):
        try:
            data = json.loads(text)
        except json.JSONDecodeError:
            data = None
        if isinstance(data, dict) and set(data) == {"url"}:
            q = parse_qs(urlparse(data["url"]).query)
            return {"kind": "json_challenge", "t": (q.get("t") or [None])[0]}
    if "captcha-delivery.com" in text or "var dd=" in text:
        return {"kind": "html_challenge_or_block"}
    return {"kind": "other", "status": resp.status_code}

Footgun: Accept: application/json often yields {"url":"https://geo.captcha-delivery.com/…"}. resp.json() succeeds. Pipelines that only catch parse errors ingest garbage rows.

Inside HTML, an inline var dd={…} object carries fields such as rt and sometimes t. Observed live (2026-08-09) on EU tenants: challenge URLs with t=bv vs t=fe correlated with different IP pressure on the same source IP across sites. Frame those as dated observations, not eternal vendor docs — DataDome can change fields.

Pro Tip

[!TIP] Pro Tip: Persist the datadome cookie per session and keep it pinned to the same egress IP while you diagnose. Discarding it every request, or replaying one cookie across a rotating pool, creates a new signal on top of whatever already failed.

A concrete incident timeline

  1. Catalog job starts through datacenter egress → wall of 403
  2. Team switches to residential rotation → still 403, bandwidth climbs
  3. Someone notices x-datadome: protected and a 770-byte HTML body
  4. Classifier finds a JSON {"url":…} path on the API Accept header
  5. Three-way curl shows residential does change one tenant and does not change another

Step 5 is the only place Premium vs Elite matters. Steps 1–4 are free if you log headers and body prefixes on every non-2xx (and on suspicious 200s).

When residential helps (and when it burns exits)

PatternMove
Fresh residential changes the outcomeKeep Elite or Premium rotation / sticky sessions
Identical challenge shell on every clean exitClient/TLS/JS layer — stop rotating
Intermittent 200s with no code changeFail-open / policy drift possible — keep content asserts
Fresh residential changes the outcome, or it does not
If fresh residential changes the outcome, keep rotation or sticky. If every Elite exit shows the same shell, stop rotating and fix the client. Sticky is 1–1440 minutes, default 30 — pin the cookie to one egress.

Aethyn ports for reproducible tests:

  • Premium HTTP 2099 / SOCKS5 1099
  • Elite HTTP 5499 / SOCKS5 3499

Example: http://aethyn-XXXXX-country-fr:PASSWORD@proxy.aethyn.io:5499

Proxies fix where and how fast you appear. They do not run the DataDome JS tag. If every Elite exit gets the same shell, move to curl_cffi or Playwright — see also silent Playwright 403s.

Three-way curl before a rewrite

Plain curl → Chrome-UA curl → residential Chrome-UA curl. Log x-datadome, Set-Cookie names, and body class. That matrix separates UA triggers from reputation from always-on challenges.

Code Snippet
PROXY="http://aethyn-XXXXX-country-fr:PASSWORD@proxy.aethyn.io:5499"
URL="https://TARGET/"
UA='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36'

echo "=== plain ==="; curl -sS -D - -o /tmp/dd-plain.body "$URL" -w "\nHTTP %{http_code}\n" | grep -iE "HTTP/|x-datadome|set-cookie: datadome|server:"
echo "=== ua ==="; curl -sS -D - -o /tmp/dd-ua.body "$URL" -A "$UA" -w "\nHTTP %{http_code}\n" | grep -iE "HTTP/|x-datadome|set-cookie: datadome|server:"
echo "=== res ==="; curl -sS -D - -o /tmp/dd-res.body "$URL" -x "$PROXY" -A "$UA" -w "\nHTTP %{http_code}\n" | grep -iE "HTTP/|x-datadome|set-cookie: datadome|server:"

Store the three body files. Diff length and whether captcha-delivery.com appears. If all three are the same challenge shell, buying another gigabyte of Elite will not change the graph — your client stack will.

Fail-open and flaky “wins”

DataDome’s documented integration behaviour includes fail-open paths: if the module cannot reach the Protection API, traffic may be treated as allowed. Intermittent 200s under load can mean protection degraded, not that your scraper got smarter. Keep content assertions on expected selectors. Celebrate only when asserts hold across a fixed URL basket for a meaningful window — not when one lucky request returned HTML.

Mistakes that waste weeks

  • Reading every 403 as “banned”
  • Forging or replaying datadome cookies across IPs
  • Spoofing only User-Agent (UA/TLS contradiction)
  • Celebrating flaky 200s without selector asserts
  • Looking for Protection-API headers (X-DataDome-isbot) in the browser — clients never see those
  • Assuming Cloudflare 1020 playbooks transfer — there is no cf-ray severity ladder here

Stay in public-data / Terms-safe scope. This is diagnosis, not a CAPTCHA bypass guide.

Continue with copy-paste detectors and branching code: Handle DataDome blocks in Python. Cross-vendor matrix: Identify which anti-bot blocked you. Sibling error posts: Akamai Reference #18, Kasada 429 misdiagnosis.

FAQ

Common questions about this article

Why is every DataDome outcome HTTP 403?
Device check, CAPTCHA, and hard ban commonly share one 403 envelope with little branding. Distinguish them with x-datadome headers, the datadome cookie, and body/challenge URL contents — never status alone.
How do I detect DataDome quickly?
Look for header x-datadome: protected (literal value protected), Set-Cookie: datadome=…, script hosts on js.datadome.co/tags.js, or captcha-delivery.com challenge links. Title is often just the bare domain — title-based detectors miss it.
Will a residential proxy remove DataDome CAPTCHAs?
No. Proxies change IP reputation and velocity. CAPTCHA and Device Check clearance need a capable client. This guide does not cover solving CAPTCHAs.
What about t=bv on a captcha-delivery URL?
Observed on live tenants (2026-08-09) as a challenge query hint that often correlates with strong IP pressure on that property. Treat it as a diagnostic hint, not a vendor-documented oracle — and never as a guarantee another IP will pass.
Share this article

Guides, integrations & docs

Continue reading

Classify DataDome before you rotate

Use Elite HTTP 5499 when reputation pressure is confirmed, Premium 2099 for volume on softer paths — and always parse the challenge body in Python first.

Back to all articles