LIVE GET/signals status200 · no-store waf request id-eSK3z6QNSo8TerrP279804cBsTioqW9JsX4S1Y77uJiBOoMOinFhg== seen from216.73.216.202 loadedat request time outcomeALLOW

/signals

This page reports and never enforces: it answers 200 whatever the policy decides, with Cache-Control: no-store. The statuses below are what a content route would have returned.

Trace a run

Paste a run's trace token from the playground to see what the backend received for that run's requests, newest first, up to 50. Requests the WAF blocked never reached the backend, so they appear only in the WAF log. Paste a WAF request id into a WAF log query (filter httpRequest.requestId = "…") to read that request's full WAF record.

1. WAF-inserted headers

6 received

Header	Value as received
`x-amzn-waf-bot-category`	`ai`
`x-amzn-waf-bot-signals`	`cloud_service_provider:aws,non_browser_user_agent`
`x-amzn-waf-bot-status`	`category:ai,name:claudebot,unverified`
`x-amzn-waf-client-ip`	`216.73.216.202`
`x-amzn-waf-token-status`	`absent`
`x-amzn-waf-waf-request-id`	`-eSK3z6QNSo8TerrP279804cBsTioqW9JsX4S1Y77uJiBOoMOinFhg==`

2. Every other request header

32 headers

Header	Value
`accept`	`/`
`accept-encoding`	`gzip, br, zstd, deflate`
`cloudfront-forwarded-proto`	`https`
`cloudfront-is-android-viewer`	`false`
`cloudfront-is-desktop-viewer`	`true`
`cloudfront-is-ios-viewer`	`false`
`cloudfront-is-mobile-viewer`	`false`
`cloudfront-is-smarttv-viewer`	`false`
`cloudfront-is-tablet-viewer`	`false`
`cloudfront-viewer-address`	`216.73.216.202:64327`
`cloudfront-viewer-asn`	`16509`
`cloudfront-viewer-city`	`Columbus`
`cloudfront-viewer-country`	`US`
`cloudfront-viewer-country-name`	`United States`
`cloudfront-viewer-country-region`	`OH`
`cloudfront-viewer-country-region-name`	`Ohio`
`cloudfront-viewer-http-version`	`2.0`
`cloudfront-viewer-latitude`	`39.95870`
`cloudfront-viewer-longitude`	`-82.99870`
`cloudfront-viewer-metro-code`	`535`
`cloudfront-viewer-postal-code`	`43215`
`cloudfront-viewer-time-zone`	`America/New_York`
`cloudfront-viewer-tls`	`TLSv1.3:TLS_AES_128_GCM_SHA256:fullHandshake`
`host`	`tripsi-demos-9ov3tnly4fng-874983800.us-east-1.elb.amazonaws.com`
`user-agent`	`Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)`
`via`	`2.0 1c7d2acc571bfdfea1aaa4496085dbda.cloudfront.net (CloudFront)`
`x-amz-cf-id`	`-eSK3z6QNSo8TerrP279804cBsTioqW9JsX4S1Y77uJiBOoMOinFhg==`
`x-amzn-trace-id`	`Root=1-6ac81d97-0326a8346c28cc2b24b4e316`
`x-forwarded-for`	`216.73.216.202, 18.68.21.101`
`x-forwarded-port`	`80`
`x-forwarded-proto`	`http`
`x-tripsignal-origin-secret`	`***`

The origin secret's name is shown and its value is redacted to ***. Seen from here: 216.73.216.202.

3. The backend policy

Outcome: allow

On a content route this request would have received HTTP 200.

Labels the policy read

Policy input	As forwarded
`bot`	`category:ai,name:claudebot,unverified`
`category`	`ai`
`signals`	`cloud_service_provider:aws,non_browser_user_agent`
`rate`	`(absent)`

Policy table top to bottom, first match wins

Outcome	Evidence the row needs	Content route
block	a specific bot name AND another signal	403 from the origin
inspect	a specific bot name on its own; handed to third-party review	200, recorded
allow	everything else: no row matched	200 ◀ this request

No policy row matched.

6. Correlation token

No well-formed tstrace token on this request, so nothing was recorded. A malformed token is ignored rather than rejected.