Download websites that use PerimeterX

Bot defence gets installed after something has already gone wrong. Nobody buys it speculatively, so finding PerimeterX on a domain is a reasonable indicator that the site has accounts worth stealing, prices worth scraping, stock worth hoarding or a checkout worth abusing. Presence in the Security category here is less a technology preference than a statement about what the business is worth attacking.

The naming needs care. The product is recorded under HUMAN Security, which is not the name it launched with, because the original company was absorbed into a larger bot management business and the branding has been migrating ever since. Fingerprints outlive brands. A detection can correspond to a site running the older sensor, the newer suite, or a bundle resold through a delivery network partner, and our label follows the code rather than the sales sheet.

The sensor is written in JavaScript and the licence is Proprietary, and the combination matters for anyone estimating spend. The product line dates to 2014 and is sold on traffic volume under enterprise agreements, not switched on for free by a small site. So the detected population skews heavily towards ecommerce, ticketing, travel, financial services and media at a size where fraud has its own line in the budget and a named owner.

As of October 2026 we detect PerimeterX on 466 sites, and the figure understates deployment for a reason specific to this category. A meaningful share of protection runs at the edge or in front of the origin, where it never places anything in the delivered page at all. Detection depends on the client side sensor appearing in the markup we receive, so a customer using only the network layer, or serving the sensor from a first party path, stays invisible to us. There is an obvious irony in a crawler measuring anti crawling software, and saying so is better than pretending the sample is complete.

Who wants the list. Competing vendors want the accounts, because a bot mitigation install is a renewal with a date on it and a champion who already believes in the problem. Security researchers want the population in order to study how defences correlate with sector, with traffic value and with the rest of the stack. Fraud and marketplace teams want to know which of their partners are protected and which are not. Checking one domain tells you whether a single site is defended. The extract tells you which parts of the web have decided that automated traffic is a cost worth paying to control, and no lookup produces that view.