Background challenge
Checking…Estimated time remaining
Waiting for AWS’s SDK to report whether this session has an active token.
EXPERIMENT 02 / INLINE CAPTCHA
The page is public. Its JSON request is protected. Send that request, inspect WAF’s response, then solve AWS’s puzzle right here.
LIVE 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.
The frontend fetches /inline-protected/demo.json with AWS token handling.
When WAF returns a CAPTCHA response, the page loads AWS’s widget and renders the puzzle below.
After a successful solve, the page retries the same request and displays the returned JSON.
MAKE A REAL REQUEST
A background challenge token is not enough for this rule. WAF checks for a recent CAPTCHA solve.
Preparing the experiment…
Solve the real AWS puzzle here. On success, this page retries the protected request.
Only observed events appear here. WAF logs contain the exact matching rule.
This is populated only when the request returns JSON successfully.
No protected response loaded yet.
CloudFront inserts challenge.js to acquire background browser tokens. This page separately loads the CAPTCHA jsapi.js from the deployed configuration, calls AwsWafCaptcha.renderCaptcha(), and retries the JSON request in onSuccess. WAF owns token validation.
The configured CAPTCHA API key is an encrypted, domain-scoped client key intended for the browser. Token values are never displayed by this demo.