Background challenge
Checking…Estimated time remaining
Waiting for AWS’s SDK to report whether this session has an active token.
THREE WAYS TO PROTECT A REQUEST
Explore a full-page CAPTCHA, a puzzle inside your page, and targeted bot detection. Every experiment sends real requests through AWS WAF.
Choose an experimentLIVE SESSION
Estimated time remaining
Waiting for AWS’s SDK to report whether this session has an active token.
Immunity time remaining
A successful CAPTCHA solve starts this demo’s 60 second immunity window.
Active status comes from AWS’s SDK. Challenge time is an upper limit estimate, because AWS does not expose its expiry timestamp. Automatic refresh can restart the estimate. CAPTCHA has a separate window. WAF validates every protected request.
Navigate to a protected page. AWS supplies the entire CAPTCHA screen, then retries your navigation after a successful solve.
Request protected JSON, see WAF’s response, and solve the puzzle without leaving the page. Watch the request retry.
Acquire a background browser token, then compare requests with and without it. AWS’s managed rules choose the response.
EXPERIMENT 01
The probe deliberately omits cookies. WAF should return 405 and x-amzn-waf-action: captcha. The response is logged below.
A normal navigation displays AWS’s verification screen. Solve its puzzle to reach the dummy protected HTML.
A valid CAPTCHA solve lasts 60 seconds in this demo. The next request after expiry requires a new solve. Content already loaded remains visible.
Ready. Probe the endpoint or open the protected page.
Only observed events appear here. WAF logs contain the exact matching rule.
The pages and controls are public. WAF protects the separate HTML or JSON requests. CAPTCHA checks human interaction; it does not provide user authentication. The background SDK is injected by CloudFront. The inline puzzle’s widget is loaded explicitly by the page.