DataDome
A real-time bot-protection service that scores every request in milliseconds from device, network and behavioural signals, common on e-commerce and classifieds.
DataDome's distinguishing claim is speed: a verdict on every single request, rendered in a couple of milliseconds, rather than a gate you pass once at the door. That design decision shapes everything a scraper experiences against it. There is no getting in and then being trusted; each request is re-judged, so a setup that worked for fifty requests can be challenged on the fifty-first when the accumulating pattern crosses a threshold.
The verdict is assembled from the layers this glossary treats separately, weighted and combined. Network reputation and address type. The TLS fingerprint, read before decryption. Header composition and order. A JavaScript-collected device fingerprint. And behaviour over the session, the pacing, the navigation shape, the presence or absence of the small human irregularities. No single signal decides; the score is the sum, which is why fixing only the address moves the number a little and clears nothing on its own.
It is concentrated in specific industries, which is worth knowing when you meet it. E-commerce, classifieds, ticketing and media are its heartland, because those are the businesses most targeted by scraping and fraud and most able to justify the cost. Recognising it is straightforward once you have seen it: a distinctive interstitial and challenge page, and response headers that name it, so you can usually confirm what you are up against rather than guessing.
The honest strategic read is that DataDome is one of the systems where the address is the smallest part of the answer. Because it leans heavily on the client fingerprint and on per-request behaviour, a trusted residential exit is necessary and nowhere near sufficient: the same handshake and the same mechanical rhythm arriving on a clean IP are exactly the contradiction it is built to catch. Coherence across every layer, held over the whole session, is the only thing that survives it.
Which is also why it is a target where a purpose-built endpoint frequently wins on economics. Keeping a bespoke client coherent against a system that retunes continuously is ongoing engineering time, and for many teams the per-request cost of a specialist is lower than the salary cost of maintaining the position themselves.
How HProxy handles it
DataDome is the clean example of our standing point that an IP is one layer. A good address raises your floor against it and cannot rescue a client whose handshake and behaviour contradict the story the address tells, which is why we pair the proxies with a scraper API for exactly these targets rather than selling a pricier IP as the fix.
Frequently asked questions
Can residential proxies bypass DataDome?
They remove one input, network reputation, and that is far from the whole score. DataDome weighs your TLS fingerprint, device fingerprint and per-request behaviour just as heavily, and any of them contradicting the address is enough on its own. A clean residential exit is necessary against it and never sufficient by itself.
How do I know a site uses DataDome?
Its challenge page has a recognisable look, and its involvement usually shows in the response headers and in the cookies set on a challenge. When a block presents as a distinctive interstitial rather than a plain 403, and the headers name the service, you can confirm what you are dealing with instead of guessing at the defence.
Why does DataDome block me mid-session when I started fine?
Because it scores every request rather than admitting you once. A pattern that looks acceptable early, request pacing, navigation shape, fingerprint stability, can cross a threshold as it accumulates, so the block lands partway through. It is not that your access was revoked; it is that the running verdict on your latest requests changed.
What actually works against DataDome?
Coherence across every layer, sustained over the session: a genuine browser fingerprint, a TLS handshake that matches the browser you claim, a trusted residential address in a plausible location, and behaviour paced like a person's. Because holding all of that against a continuously retuned system is real engineering effort, a specialist scraper endpoint is often the more economical route for hard DataDome targets.
Back to the full glossary.