Bypass do PerimeterX, hold captcha incluído.

Um bypass do PerimeterX (agora HUMAN) sem navegador. A Takion devolve cookies _px3 / _px2 válidos (e qualquer outro relacionado) e passa pelo captcha de segurar (pxhc) em um POST, para que suas requisições passem, ou o header x-px-authorization se você estiver acessando um app mobile.

Última atualização · Cobertura testada contra um alvo PerimeterX / HUMAN ao vivo.

Sendo bloqueado pelo PerimeterX?

O PerimeterX (agora HUMAN) rejeita tráfego que não vem de navegador até que sua requisição carregue um conjunto de cookies _px3 / _px2 válido, e passa pelo captcha de segurar (pxhc) quando ele é servido. Em alvos de SDK mobile a mesma confiança é carregada no header x-px-authorization. A Takion gera tudo isso e devolve em um único POST, sem navegador headless e sem gesto para simular do seu lado, para que sua requisição passe. Uma chave cobre todos os muros suportados; você traz seu próprio proxy para a requisição de dados.

O acesso ao teste é controlado

Um bypass do PerimeterX pode ser usado para fraude, então o acesso ao teste não é automático. Se você quiser avaliá-lo, fale com a gente antes e conte qual é o seu caso de uso.

Como o PerimeterX funciona

O PerimeterX (agora HUMAN Security) monta um score de risco a partir de um fingerprint de dispositivo e de uma análise profunda de telemetria do seu comportamento, coletada durante um captcha de segurar ou interações normais na página por meio de uma série de posts criptografados. Seus desafios giram o tempo todo, e é isso que torna difícil acompanhá-los na mão.

A Takion gera e envia ao PerimeterX todos os dados de que ele precisa para colocar sua sessão na whitelist, passa pelo captcha de segurar quando ele aparece e devolve os cookies _px3 / _px2 em seu estado aprovado, junto com qualquer outro token exigido. Um POST, sem navegador, sem gesto para simular do seu lado. Os cookies voltam prontos para reutilizar.

Apps mobile que usam o SDK do PerimeterX funcionam do mesmo jeito: os tokens voltam como um conjunto de headers x-px-* em vez de cookies. Mesmo padrão, valores e cálculo diferentes. Nós cobrimos os dois.

  • Desafios que a Takion cobre
  • Captcha de segurar (pxhc)
  • Cookies de risco _px3 / _px2
  • Desafio mobile x-px-authorization

O que uma chamada devolve

Um POST no endpoint do PerimeterX devolve exatamente os tokens que o muro espera, prontos para reutilizar contra o seu alvo.

_px3 / _px2 (and any other related one)

o cookie de risco principal em seu estado aprovado

x-px-authorization

o header que os alvos do SDK mobile esperam

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>" }'

Ler a documentação do PerimeterX / HUMANA mesma chave para todo muro. O mesmo formato de JSON para todo fornecedor.

How the PerimeterX bypass works, end to end

No browser, no gesture to fake. Five moves from blocked to data.

  1. 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. 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. 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. 4

    You get _px3 back, passed

    The response carries the _px3 cookie in its passed state plus an x-px-session-id you can feed to the optional /tls helper to keep the session hot.

  5. 5

    You replay and you are in

    Attach _px3 to 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 _px3 or _px2 cookie in the response. The primary risk cookie. If you see it set on first load, PerimeterX is scoring the session. Older deployments still set _pxvid and _pxhd alongside it.
  • A _pxAppId string in the page source. It looks like PX followed 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-block or 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-authorization header 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.

Alguns sites que usam PerimeterX

PerimeterX / HUMAN protege estes sites. O Takion o resolve em cada um, então um bypass de zillow é o mesmo POST único que qualquer outro muro.

Perguntas frequentes sobre o bypass do PerimeterX

Sim. A Takion resolve o hold-captcha de segurar e devolve o token pxhc junto com cookies _px3 / _px2 válidos, então você nunca renderiza o botão nem simula o gesto.
Sim, damos suporte e resolvemos o init (a geração normal de px na página web).
Sim, basta falar com a gente para colocar seu app/site na whitelist.

Todos os outros muros

Lance seu bypass do PerimeterX hoje.

Teste gratuito e, depois, uma única chave para todos os muros. Primeira chamada em menos de uma hora.