Media
5 items
Description
answers akamai and datadome challenges in the tab you're browsing. your browser sends every request; the solver runs in your infra. no more anti-bot blocks — in the browser you are already using. xhr.dev is a self-hosted anti-bot solver: a docker image on your own hosts, no third-party api call, nothing to explain in a security review. this extension is a client for it. it watches the tab you are browsing, and when datadome or akamai puts a challenge in front of you, it answers it — usually before you have noticed one was there. what it solves • datadome — interstitial, captcha, and the interstitial-to-captcha escalation • akamai bot manager — the _abck session, run until the cookie is accepted • akamai sbsd — the fifo ledger, one per document snapshot who sends the submission is the whole point the solver computes the sensor values. your chrome makes every request. nothing is forged: the computed values are spliced into the request the browser is already sending, so the tls fingerprint, the client hints and the cookie jar are genuinely yours. both vendors bind the clearance cookie to whoever submitted it. that is why it has to work this way — and why a cookie bought from somebody else's api is already spent by the time it reaches you. nothing leaves your network the extension talks to exactly one host: the solver you point it at. no external solving api, no telemetry, no analytics, no vendor in the loop. give it no host and it does nothing at all. setup 1. options → your solver host. an api key too, if your deployment gates on one. a self-hosted container is licence-gated at startup and needs none. 2. for akamai properties, list the origins. those have to be instrumented from the first byte — a sensor script cannot be un-run. 3. browse. a challenge starts a solve by itself, and the popup carries the full transcript of the exchange, round by round. requirements an xhr.dev solver you can reach: a container on your own hosts, or a trial box issued to you. see docs.xhr.dev. chrome shows its "is debugging this browser" banner while a solve runs. that is the debugger api being used to rewrite the request, and there is no way to attach without it.