Partial chain validation · 11 October 2026

Redis Cloud production-side proof

In four tests using a researcher-owned account, a local document with the QA origin made credentialed requests to the production console. Each test created a temporary API key that authenticated a separate request to the Redis Cloud API without browser cookies.

Reproduced runs4 / 4
Key creation from QA originHTTP 200
Cookieless API without keysHTTP 401
Cookieless API with new keysHTTP 200
Temporary key deletionHTTP 204
Temporary keys remaining0
Own email shown in local browserHTTP 200

Per-run results

RunOrigin readKey createdNo keysWith keysDeleted
1200200401200204
2200200401200204
3200200401200204
4200200401200204

Validation boundary

The QA-origin document was supplied locally by Playwright. No request was sent to the QA host. An authenticated production navigation with the public entry URL made zero requests to that entry and loaded Redis’s own databases module. The public entry has not been loaded by the live QA application. A live one-click account takeover has not been verified. The QA host is absent from the program’s current structured scope.

Published artifacts

Sanitized machine-readable results · Harmless Module Federation marker

This page contains no account identity, cookie, API key, or secret.