Evidence ev_01m67ew76sb4aqw8k0j1db48wn: Crusado access
This page shows one reading behind the statements on Crusado's page: what CasinoGuard captured, when and from where, how, and the files kept as proof, each with its SHA-256 so anyone can check it is unchanged.
- Evidence: ev_01m67ew76sb4aqw8k0j1db48wn
- Topic: Access
- Source: crusado.com, as CasinoGuard's own visit found it (observed)
- Scope: United Kingdom (GB)
- Captured: 2026-10-30 22:28 UTC
- Result: read, the first version of what the source states
- Read by:
oasis-access@1
Crawl
- Crawl: 01m67evnwjktcx4fhk6qzyxpqk (done)
- Requested: 2026-10-30 22:28 UTC
- Started: 2026-10-30 22:28 UTC
- Finished: 2026-10-30 22:28 UTC
- Collected with:
[email protected] running oasis-access@1 - Looked from: United Kingdom (GB) · Desktop · crusado.com · language en
- Proxy: pool
uk-residential-di(Residential, GB) - Exit network: not recorded (where the casino saw the visit come from)
View 1: access
- Asked for: https://crusado.com
- Landed on: https://crusado.com/
- Redirects: https://crusado.com → https://crusado.com/ (307) → https://crusado.com/?__cf_chl_rt_tk=AlzD7tOcpOmtVv6eSY9A19ZTyAFTxmj7oGfNJo6GKQY-1793399320-1.0.1.1-LTIKrnyEIJrKmeJQ6j_H0JTBCZdwqSKTAG2Ikf3cNL8
- HTTP status: 403
- Captured: 2026-10-30 22:28 UTC
- Steps: open https://crusado.com (as a visitor typing the address: no path, nothing clicked); follow https://crusado.com → https://crusado.com/ → https://crusado.com/?__cf_chl_rt_tk=AlzD7tOcpOmtVv6eSY9A19ZTyAFTxmj7oGfNJo6GKQY-1793399320-1.0.1.1-LTIKrnyEIJrKmeJQ6j_H0JTBCZdwqSKTAG2Ikf3cNL8 (every redirect, the server's and the page's own)
Screenshot of what it read:
| File | Size | SHA-256 |
|---|---|---|
| Screenshot of what it read | 16.5 KB | 45bc09184ca9750e127051d61ac4460199cb31c82db479c5a8c1640254529595 |
| Web archive (WACZ) | 1.2 MB | e8dc7156743011ffc7fa6a49a802228f6fd2e94d4366c8085f8e468f2095381a |
What it read
The reading as the worker sent it:
{
"result": "blocked",
"block_kind": "cloudflare",
"final_host": null,
"http_status": 403
}
How to check it
- The web archive is what the browser received during the crawl: every response with its request, and each view as rendered, listed as a page of its own (a crawl's views share one archive). Download it and open it in ReplayWeb.page to browse each page as it was.
- Each file's SHA-256 is that of the file when it was received; recompute it to check the file is unchanged.
- Cookies, logins and tokens are left out of every file, and so is the proxy's credential.
- The Markdown version and plain-text version of this page say the same.