Is this site behind Kasada?

Cryptographic proof-of-work bot defence used by streaming, retail, and travel — recognisable by the `x-kpsdk-*` headers.

Free diagnostic • Confidence scoring • Signal-by-signal breakdown • Recommended client configuration

URL to check

Try:

Verification keeps this tool free from abuse. For diagnostic and developer use only — run checks on sites you are authorised to access.

What is Kasada?

Kasada uses an in-browser proof-of-work to make automation expensive: the browser must compute a token before each protected request. Combined with a heavy JS fingerprint, it filters most automated traffic.

Read the full Kasada glossary entry

How Kasada protects sites

›Proof-of-work token computed in-browser (`x-kpsdk-ct`)
›`x-kpsdk-cd` and `x-kpsdk-v` request headers
›Heavy obfuscated JS sensor
›Server-side challenge enforcement at every endpoint

Detection signals we look for

✓x-kpsdk-* request or response headers
✓Inline script from /_kpsdk/ or kpsdk.com
✓429 / 403 with x-kpsdk-fc failure code

Recommended Scrappey client configuration

For authorised access only — your own properties, contractually permitted scraping, QA, monitoring, accessibility audits, and similar use cases. Always respect the site's terms of service and applicable law.

→Run a full browser engine — the proof-of-work token is computed client-side and expects a real JS runtime.
→Use Scrappey browser mode so the x-kpsdk token is produced by the page itself.
→Keep the proxy region aligned with the request; geo mismatches lower the score.
→Refresh sessions regularly — the issued tokens are short-lived.

Create a free account to run the configuration above — free demo trial, no card required.

Kasada FAQ

Why is the proof-of-work mandatory?

The PoW token is verified server-side on every request. The only way to produce a valid token is to run Kasada's JS in a real engine, the way the protection expects.

Related concepts

Deeper reading on the techniques and signals that surround Kasada.

Anti-Bot Detection

Glossary

Browser Fingerprinting

Glossary

Anti-Bot Vendor Detection Cheatsheet

Glossary

Concept map

How anti-bot protection fits together

Hover a vendor or technique to see the connections. Click any node to read the full glossary entry. The lines show which detection techniques each vendor leans on.

6 vendors · 8 techniques · 27 connections

Hover · click a node

Vendor Technique

Detect other anti-bot vendors

Or run a generic check across all vendors

Integrations

n8n

Automate workflows visually. Streamline data collection processes.

n8n Template

Pre-built template for modern websites. Simplifies Scrappey integration.

RapidAPI

Access via API marketplace. Easy integration with comprehensive docs.

Apify

Scalable actor-based automation. Reliable browser rendering.

MCP Server

AI-powered browser automation. Intelligent session management.

Scrappey CLI

Scrape from your terminal. One command, pipeable output, CI-ready.

Claude Code Skill

Portable skill for Claude Code + Codex. Browser-backed data access on demand.

LangChain

LangChain connector — clean web data for any chain or agent.

LlamaIndex

LlamaIndex reader — load modern web pages straight into RAG.

Zapier

Connect with 7,000+ apps. Automate workflows easily.

Make

Visual workflow automation. Connect with 1,000+ apps easily.

Start building with Scrappey

Try it free. No subscription, no credit card, instant setup — your trial is waiting.

Join the Discord community