// vendor intelligence
what datadome detects
datadome is a edge-waf vendor. it declares native ip reputation (3/3), native js fingerprint (3/3), native behavioral (3/3), native challenge (3/3), strong server coherence (2/3) capability. below: the layers it enforces and the cookie, endpoint, and header tells it leaves.
enforced detection layers
| detection layer | capability | what it covers |
|---|---|---|
| tls / network fingerprint | unaddressed | the ja3/ja4 clienthello and http/2 settings signature the edge reads before any javascript runs. |
| ip reputation | 3/3 native | asn, proxy-class, and abuse-history scoring of the connecting address. |
| js fingerprint | 3/3 native | canvas, webgl, navigator, font, and audio signals collected in-page. |
| behavioral | 3/3 native | mouse, keyboard, and timing biometrics read from interaction cadence. |
| challenge | 3/3 native | interactive or invisible captcha and proof-of-work gates. |
| attestation | unaddressed | hardware or os-backed integrity checks (webauthn, play integrity, device attestation). |
| server coherence | 2/3 strong | cross-checking headers, tls, ip, and js for internal consistency. |
unaddressed means this tool type does not operate at that layer, so it is not a failing score. a red 0/3 is a real, declared score of zero. both are declared capability, not live pass-rates.
tells
- cookies
- datadome
- endpoints
- api-js.datadome.co/js/
- header tells
- datadome, x-datadome, x-dd-b
wasm boring_challenge probes canvas/webgl + device coherence, ip-reputation weighted; 403 dd{} JSON redirects to geo.captcha-delivery.com.
questions
- what does datadome detect?
- it declares native ip reputation (3/3), native js fingerprint (3/3), native behavioral (3/3), native challenge (3/3), strong server coherence (2/3) capability. layers not listed are not enforced by datadome.
- what are datadome's tells?
- header/script tells: datadome, x-datadome, x-dd-b. cookies: datadome. endpoints: api-js.datadome.co/js/.
sites defended by this vendor
other vendors
where to go from here
layer intensities are catalog-declared (0..3), confirmed, and the catalog carries no capture date for this record. layer definitions in the glossary.