Evidence ev_01m66er0jvr64zs2yvsb2hjh4m: 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_01m66er0jvr64zs2yvsb2hjh4m
- Topic: Access
- Source: crusado-e.com, as CasinoGuard's own visit found it (observed)
- Scope: United Kingdom (GB)
- Captured: 2026-10-30 13:07 UTC
- Result: read, the first version of what the source states
- Read by:
famagousta-access@1
Crawl
- Crawl: 01m66epvj455ww9tcx28rmgezx (done)
- Requested: 2026-10-30 13:06 UTC
- Started: 2026-10-30 13:06 UTC
- Finished: 2026-10-30 13:07 UTC
- Collected with:
[email protected] running famagousta-access@1 - Looked from: United Kingdom (GB) · Mobile · crusado.com · language en
- Proxy: pool
uk-residential(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-e.com/en/
- Redirects: https://crusado.com/ (307) → https://crusado-e.com/ (200) → https://crusado-e.com/en/
- HTTP status: 307
- Captured: 2026-10-30 13:07 UTC
- Steps: open https://crusado.com/ (as a visitor typing the address: no path, nothing clicked); follow https://crusado.com/ → https://crusado-e.com/ → https://crusado-e.com/en/ (every redirect, the server's and the page's own)
Screenshot of what it read:
| File | Size | SHA-256 |
|---|---|---|
| Screenshot of what it read | 50.5 KB | ac0ae9bd0a74c7965771e9e9f65ad4d0bfd506c14aa4ce4218d444fe9b3970d8 |
| Web archive (WACZ) | 3.7 MB | 3bf3424cccddda58b1d2f72d2888f34fe983d96d7dc00b0f69d391a7033081ea |
What it read
The reading as the worker sent it:
{
"result": "available",
"block_kind": null,
"final_host": null,
"http_status": 200
}
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.