Обход PerimeterX, включая hold-капчу.
Обход PerimeterX (теперь HUMAN) без браузера. Takion возвращает валидные cookie _px3 / _px2 (и любые связанные с ними) и проходит капчу press-and-hold pxhc за один POST-запрос, чтобы ваши запросы проходили, — или заголовок x-px-authorization, если вы работаете с мобильным приложением.
Последнее обновление · Покрытие протестировано на живой цели PerimeterX / HUMAN.
PerimeterX вас блокирует?
PerimeterX (теперь HUMAN) отклоняет небраузерный трафик до тех пор, пока ваш запрос не будет нести валидный набор cookie _px3 / _px2, и проходит капчу press-and-hold (pxhc), когда она появляется. На целях с мобильным SDK то же доверие переносится в заголовок x-px-authorization. Takion генерирует их и возвращает в одном POST-запросе, без headless-браузера и без жестов, которые нужно имитировать на вашей стороне, так что ваш запрос проходит. Один ключ покрывает каждую поддерживаемую стену; для запроса к данным вы используете собственный прокси.
Доступ к пробной версии ограничен
Обход PerimeterX можно использовать для мошенничества, поэтому пробный доступ выдаётся не автоматически. Если хотите его оценить, сначала свяжитесь с нами и расскажите о своём сценарии использования.
Как работает PerimeterX
PerimeterX (теперь HUMAN Security) строит risk-оценку из отпечатка устройства и глубокого анализа телеметрии вашего поведения, собранной во время капчи press-and-hold или обычных взаимодействий со страницей через серию зашифрованных POST-запросов. Его проверки постоянно меняются — именно поэтому за ними так тяжело поспевать вручную.
Takion генерирует и отправляет PerimeterX все данные, необходимые, чтобы добавить вашу сессию в белый список, проходит капчу press-and-hold, когда она появляется, и возвращает cookie _px3 / _px2 в пройденном состоянии вместе с любым другим нужным токеном. Один POST-запрос, без браузера и без жестов, которые нужно имитировать на вашей стороне. Cookie возвращаются готовыми к воспроизведению.
Мобильные приложения на SDK PerimeterX работают так же: токены возвращаются не как cookie, а как набор заголовков x-px-*. Тот же принцип, другие значения и вычисления. Мы закрываем оба случая.
- Проверки, которые закрывает Takion
- Капча press-and-hold (pxhc)
- Risk-cookie _px3 / _px2
- Мобильный челлендж x-px-authorization
Что возвращает один вызов
Один POST-запрос к эндпоинту PerimeterX возвращает именно те токены, которых ждёт стена, — готовые к отправке на ваш целевой сайт.
_px3 / _px2 (and any other related one)основной risk-cookie в пройденном состоянии
x-px-authorizationнабор заголовков, который ждут цели с мобильным SDK
curl -X POST https://px{web/hc/mobile}.takionapi.tech/generate \
-H "Authorization: Bearer $TAKION_KEY" \
-H "Content-Type: application/json" \
-d '{ "url": "<the url of the page you aim to visit>", "proxy": "<your session proxy>", "extra": "<challenge or website details>" }'Читать документацию по PerimeterX / HUMANОдин ключ на все стены. Одна структура JSON для каждого вендора.
How the PerimeterX bypass works, end to end
No browser, no gesture to fake. Five moves from blocked to data.
- 1
Point Takion at the target
Grab the PerimeterX app id (
_pxAppId) and the page URL of the site you are hitting. That is all Takion needs to know which wall it is minting for. - 2
You POST it to Takion
Send the app id, page URL, your session proxy, and the user-agent you will replay to the web endpoint. One call, no SDK to embed.
- 3
We mint the session server-side
Takion runs the encrypted collector posts PerimeterX expects, builds the device signals its risk engine scores, and clears the press-and-hold captcha if the site serves one. No browser, no page render.
- 4
You get _px3 back, passed
The response carries the
_px3cookie in its passed state plus anx-px-session-idyou can feed to the optional/tlshelper to keep the session hot. - 5
You replay and you are in
Attach
_px3to your own request, send it through the same proxy with the same user-agent, and PerimeterX sees a trusted session and serves the data.
The PerimeterX surfaces, decoded
One vendor, three shapes. Takion covers each on its own endpoint:
_px3 / _px2- the primary risk cookies PerimeterX sets on the web, returned in their passed state
Press-and-hold (pxhc)- the "press & hold to confirm you are human" block page, solved async and resolved back to a _px3
x-px-authorization- the header the iOS / Android SDK carries the same trust in, with x-px-original-token and x-px-context on some apps
x-px-session-id- Takion's session id, feed it to /tls to send more session-bound requests without re-minting
_pxAppId- the target's PerimeterX app id you hand Takion so it mints against the right deployment
How to tell if a website is protected by PerimeterX
Before you pick an endpoint, confirm what you are actually up against. A PerimeterX protected website leaves the same fingerprints every time, and you can check all of them from a single request in your browser devtools:
- A
_px3or_px2cookie in the response. The primary risk cookie. If you see it set on first load, PerimeterX is scoring the session. Older deployments still set_pxvidand_pxhdalongside it. - A
_pxAppIdstring in the page source. It looks likePXfollowed by eight characters (PXu6b0qd2S). That is the target's PerimeterX deployment id, and it is the one value Takion needs to mint against the right wall. - Requests to
*.px-cloud.net,*.px-cdn.net, or*.perimeterx.net. The collector endpoints the sensor posts encrypted telemetry to. First-party deployments proxy these behind a random path on the site's own domain, so also watch for an unexplained POST that fires on every page. - A press-and-hold block page. "Press & Hold to confirm you are human." That is the pxhc captcha, and it is PerimeterX by definition.
- A 403 with a
x-px-blockor reference-id body. The block page carries a PerimeterX reference id you can quote to the site owner. If your scraper gets a short 403 HTML page with a reference id and nothing else, that is PX detection firing. - An
x-px-authorizationheader on mobile. If you are proxying an iOS or Android app rather than a website, the trust rides in headers instead of cookies. Same vendor, different surface.
Bot Defender, Code Defender, and which one is blocking you
PerimeterX was acquired by HUMAN Security in 2022 and the products were renamed, which is why the same wall shows up under several names. Only one of them is the thing that 403s your scraper:
Bot Defender- the bot detection and bot management product, and the one you are hitting. It sets _px3 / _px2, serves the press-and-hold captcha, and issues the 403. When someone says "PerimeterX bypass" this is what they mean, and it is what Takion covers.
Code Defender- client-side supply-chain monitoring. It watches the scripts running on the site's own pages for skimmers and unauthorized data access. It does not challenge your requests, so it is not in the path of a scrape.
Account Defender- post-login account-takeover scoring. It runs on the site's authenticated traffic and reacts to account behavior, not to the session handshake. Clearing Bot Defender does not touch it.
HUMAN / PerimeterX- the same company. HUMAN is the current brand, PerimeterX is the name most of the tooling, cookies, and documentation still carry. Search either and you land on the same wall.
Why request-based beats a headless browser here
The browser way to beat PerimeterX is a fleet of headless instances that render the page, fake a mouse path, and hold down the press-and-hold button for the right duration while the SDK streams encrypted telemetry back to *.perimeterx.net. It works until PerimeterX rotates the challenge, which it does constantly, and then every one of your instances is patching in real time.
Takion skips the browser entirely. We reverse the collector protocol and generate the payload directly, so a web solve is one HTTP round trip and a mobile solve is a header set you merge into your request. No emulator farm, no gesture timing to tune, no container to babysit when the challenge changes overnight. You send JSON, you get the token.
PerimeterX errors, and what each one is telling you
PerimeterX does not return useful error text, so the status code and the block shape are the diagnosis. These are the ones you will actually see:
403 + block page- the standard PerimeterX block. Your request had no valid _px3, or the one it carried was rescored and failed. Mint a fresh session rather than retrying the same cookie.
403 + press-and-hold- PerimeterX decided you are suspicious but not hopeless, so it served the pxhc captcha instead of a flat block. Solve it on the hc endpoint and you get a passed _px3 back.
403 with a valid cookie- a consistency break, not a bad token. The cookie is bound to the IP and user-agent it was minted under. See the list below.
429- rate limiting, usually the site's own rather than PerimeterX's. Slow the request pace or widen your proxy pool. Re-minting will not help here.
captcha loop- you solve the hold captcha and it serves another one. That is a reputation problem in the proxy, not a solve problem. Move to a cleaner IP range and it stops.
How to prevent being detected by PerimeterX
A valid _px3 is necessary, not sufficient. Getting the token is the easy half; staying trusted after you replay it is where most integrations fail. PerimeterX rescoring watches for these the moment you send the request:
- IP mismatch. The cookie is bound to the IP it was minted under. Solve behind the proxy you will actually send from.
- User-agent drift. PerimeterX ties the session to the user-agent it was built against. Replay the exact one Takion was given, do not swap it.
- fast_mode on a hard target. The quick solve trades a slightly weaker PX score for speed. On aggressive deployments, drop it and let the full solve run.
- Cookie reuse across sessions. One _px3 is one session on one IP. Rotate the IP or burn the session, and re-mint.
- Bad-reputation proxies. Flagged datacenter ranges score poorly before any challenge. Clean residential or ISP proxies clear the reputation gate first.
The one rule that kills most 403s
Mint under the same proxy and user-agent you replay from, and send the token Takion hands back verbatim. PerimeterX's whole model is consistency scoring across the session. Match the fingerprint it trusted and you stay cleared.
Некоторые сайты на PerimeterX
PerimeterX / HUMAN защищает эти сайты. Takion проходит его на каждом, так что обход zillow это тот же один POST, что и любая другая стена.
FAQ по обходу PerimeterX
- Да. Takion проходит hold-капчу press-and-hold и возвращает токен pxhc вместе с валидными cookie _px3 / _px2, так что вам не нужно ни рендерить кнопку, ни имитировать жест самостоятельно.
- Да, мы поддерживаем и проходим init (обычную генерацию px на веб-странице).
- Да, просто свяжитесь с нами, чтобы добавить ваше приложение/сайт в белый список.
Любая другая стена
Запустите обход PerimeterX уже сегодня.
Бесплатный доступ, потом один ключ на все стены. Первый вызов — меньше чем за час.