Skip to main content

CAPTCHA guide

HUMAN (PerimeterX)

A behavioural sensor and the 'Press & Hold' button decide who gets through.

Difficulty: Very high
Risk engine
Exploded concept drawing of how the HUMAN challenge is built

HUMAN Security, previously PerimeterX, is an enterprise bot-management platform. Its visible challenge is the well-known "Press & Hold" button, but the real verdict comes from a sensor script that gathers browser and behaviour signals. On many sites the button never appears and the whole check runs in the background.

How to identifyLink to How to identify

  • A #px-captcha element with a "Press & Hold" button
  • Cookies named _px3, _pxvid, _pxhd, _pxde and pxcts
  • Calls to px-cloud.net, px-cdn.net or a first-party collector path
  • An X-PX-Authorization header on protected requests
  • A page titled "Access to this page has been denied", or a challenge overlay
  • Obfuscated sensor scripts such as init.js and captcha.js

How it worksLink to How it works

  1. The sensor script gathers browser, canvas, WebGL, font and behaviour signals.
  2. It sends that telemetry to the collector, which sets or refreshes _px3.
  3. Low-risk sessions go through silently. Suspicious ones get Press & Hold.
  4. The button measures how long it is held, pointer pressure, movement during the hold and timing consistency.
  5. A successful hold yields a verification token that the collector validates.
  6. Protected requests then need the resulting cookies, and on some sites an X-PX-Authorization header as well.
  7. Scoring never stops: a valid cookie can be downgraded later if the session starts acting like a bot.

Free & open-source bypass methodsLink to Free & open-source bypass methods

Tool What it does Success Rate Link
Patchright / Camoufox Stealth browsers for the sensor and the Press & Hold step 40–70% Kaliiiiiiiiii-Vinyzu/patchright-python · daijro/camoufox
DrissionPage Real Chromium with fine control of pointer events 35–65% g1879/DrissionPage
SeleniumBase UC mode Selenium with patches for sensor-heavy pages 35–60% seleniumbase/SeleniumBase
Playwright + CDP input Sends native pointer events for the hold 30–60% microsoft/playwright-python
curl_cffi Mimics browser TLS for sessions already warmed up 20–45% lexiforest/curl_cffi

Practical approachLink to Practical approach

  1. Combine a real browser, a residential IP and a persistent profile.
  2. Let the sensor script load and send its telemetry. Never block the collector.
  3. If Press & Hold appears, press with a genuine pointer event, hold for a few natural seconds while moving slightly, then let go.
  4. Wait for the overlay to vanish and the protected content to load.
  5. Keep _px3, _pxvid and the rest of the cookie jar for later requests.
  6. If you are still denied, start again with another profile and IP instead of hammering retries.

Practical tipsLink to Practical tips

  • Hold time is only one signal. Pressure, small movements and timing consistency are checked too.
  • Having a _px3 cookie proves nothing, since one is set after failed attempts as well.
  • HUMAN often penalises profiles and cookies reused from earlier visits. Try both fresh and warmed sessions.
  • Headless Chrome is challenged hard. Headful or anti-detect browsers fare better.
  • What you do after the challenge also counts: slow down and avoid machine-like request bursts.
  • Collector domains and script names change, so rely on cookie and header patterns rather than URLs.

Skip the solver: let BrowserSolver handle HUMAN

Website AntiBot runs a real browser session with matching TLS, headers, cookies and IP, clears the challenge, and returns the page. You send a URL, you get HTML back.

HUMAN unlock guide →

For education and authorized testing only. Respect the law, privacy, and the terms of the sites you work with. Difficulty labels are editorial estimates. Adapted from the CC0 community field guide on GitHub.