DataDome block page
DataDome scored the request as automation and served its own interstitial — usually a 403 carrying a datadome cookie and a captcha, rather than the page you asked for.
A proxy fixes part of this. IP reputation is one input of several, and it is the one a proxy fixes. If your fingerprint is wrong, better addresses raise the score without clearing the block.
Why it happens
IP reputation: datacenter and known-proxy ranges score badly before anything else is examined.
A TLS or HTTP/2 fingerprint that does not match the claimed browser.
Behavioural signals — no mouse movement, requests arriving at machine-perfect intervals.
A missing or stale datadome cookie across a session.
How to fix it
- Raise the IP reputation first: residential or mobile exits start from a much better score.
- Keep the datadome cookie for the whole session rather than starting fresh on every request.
- Make the fingerprint coherent — the handshake, the header order and the User-Agent all have to agree.
- Add human-scale variance to timing. Perfectly regular intervals are one of the strongest signals there is.
FAQ
What does DataDome mean?›
Why am I getting DataDome?›
How do I fix DataDome?›
Will a proxy fix DataDome?›
Going deeper
Other errors
Stop getting DataDome
Residential IPs across 199 countries, from $7.35/GB — no commitment, no monthly plan.
Get residential IPs →