# Evidence ev_01m67exn5kprknthsvsw4ys7p7: Crusado access

This page shows one reading behind the statements on [Crusado's page](https://casinoguard.ai/casinos/crusado): 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_01m67exn5kprknthsvsw4ys7p7
- **Topic:** Access
- **Source:** crusado-e.com, as CasinoGuard's own visit found it (observed)
- **Scope:** United Kingdom (GB)
- **Captured:** 2026-10-30 22:29 UTC
- **Result:** read, the first version of what the source states
- **Read by:** `oasis-access@1`

## Crawl

- **Crawl:** 01m67evpc023backwnnj04tnn6 (done)
- **Requested:** 2026-10-30 22:28 UTC
- **Started:** 2026-10-30 22:28 UTC
- **Finished:** 2026-10-30 22:29 UTC
- **Collected with:** `cgd-worker@0.1.0 running oasis-access@1`
- **Looked from:** United Kingdom (GB) · Mobile · 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-e.com/en/
- **Redirects:** https://crusado.com → https://crusado.com/ (307) → https://crusado-e.com/ (200) → https://crusado-e.com/en/
- **HTTP status:** 200
- **Captured:** 2026-10-30 22:29 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-e.com/ → https://crusado-e.com/en/ (every redirect, the server's and the page's own)

Screenshot of what it read:

[![Screenshot of what it read](https://casinoguard.ai/evidence/01m67exn1tf9275zt5jpkx8q3p/screenshot/0)](https://casinoguard.ai/evidence/01m67exn1tf9275zt5jpkx8q3p/screenshot/0)

| File | Size | SHA-256 |
| --- | --- | --- |
| [Screenshot of what it read](https://casinoguard.ai/evidence/01m67exn1tf9275zt5jpkx8q3p/screenshot/0) | 7.6 KB | `cce0be2f7af4f6fd9334eb043c7a93cb9c697e2fe548dd6f67c967daaa747661` |
| [Web archive (WACZ)](https://casinoguard.ai/evidence/01m67exn1tf9275zt5jpkx8q3p/archive) | 2.0 MB | `ee42ed2e6bd22ad1ea0007e8571d68e3741e783a7b9a74937c604d59b2777f5f` |

## What it read

The reading as the worker sent it:

````json
{
    "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](https://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](https://casinoguard.ai/casinos/crusado/evidence/ev_01m67exn5kprknthsvsw4ys7p7.md) and [plain-text version](https://casinoguard.ai/casinos/crusado/evidence/ev_01m67exn5kprknthsvsw4ys7p7.txt) of this page say the same.