G2

Software reviews

Stacks DataDome behind Cloudflare, so one 403 carries the markers of two products at once.

G2 shows what a layered edge looks like on the wire. A single 403 arrives with Cloudflare's __cf_bm cookie and cf-ray header, DataDome's x-datadome, x-dd-b, and x-datadome-cid headers, a datadome cookie with a one-year lifetime, and references to both the Cloudflare challenge platform and DataDome's captcha delivery host.

Layering is common and it complicates diagnosis, because the marker you happen to notice first may not belong to the product that made the decision. The rule of thumb is that the more specific verdict header wins: x-dd-b names a DataDome block, whereas __cf_bm merely proves Cloudflare is in the path.

What is in front of it

Status codes

403 Layered block

Blocked. Observed behaviour.

A refusal carrying markers from both products in the stack. The DataDome headers identify which one decided.

What triggers it

How to confirm it

What to do about it

HTTP/2 403
x-dd-b: 2
x-datadome: protected
x-datadome-cid: AHrlqAAAAAMAZc-WcMV57acAoE9qgA==
set-cookie: datadome=GLGPOXLEKAsX3BfQ8z5Gn...; Max-Age=31536000; Path=/; Secure
set-cookie: __cf_bm=pYme6xQ5WCVHn3NKSJQ95V...; HttpOnly; Secure; Path=/
server: cloudflare
cf-ray: a32711dd0caaa13a-IAD

Notes

See also