Perimeter X Web

A PerimeterX bypass for website. Takion generates the PerimeterX web cookies the website expects, including _px3, _pxcts, _pxvid, ..., so your requests can pass.

Trial and plan access is gated. A PerimeterX bypass can be abused for fraud, so trial access is not automatic, and PXHC additionally requires your key to be whitelisted for the service. Please contact us on Discord or via mail , we'll need to verify your business first.

Check our example bundles in order to validate your implementation against our validate ones, with correct headers order, TLS and flow from our Github repo

What is PerimeterX Web?

PerimeterX, now HUMAN Security, builds a risk score from a device fingerprint and a deep telemetry analysis of your behavior, gathered through a series of encrypted posts as you use the page. It sets a _px3 cookie that carries your trusted session. Its challenges rotate constantly, which is what makes it hard to keep up with by hand.

The web trust lives in the _px3 cookie. Mobile apps running the PerimeterX SDK carry the same trust in an x-px-authorization header set instead (see PerimeterX Mobile).

How to Detect if a website is Using PerimeterX

If a site sets a _px3 cookie, it is running PerimeterX / HUMAN. When traffic looks automated it serves a press-and-hold ("press and hold to confirm you are human") captcha before granting acces, that hold captcha is handled by the Hold Captcha flow. Common fingerprints:

• A _px3 cookie on the response.

• A press-and-hold captcha page instead of the content.

• Collector posts to *.perimeterx.net or *.px-cloud.net.

Example of PerimeterX-Protected Websites

Some applications known to use PerimeterX for websites protection include:

Zillow
Walmart
PrizePicks
TextNow
SkyScanner
StockX
Grubhub
Fanatics
Crunchbase

Our API

Takion automates the whole challenge flow and returns the _px3 cookie alongside any other generated one during the resolution, so you can access protected sites without solving anything yourself. Continue to the reference