context safety score
A score of 49/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
malicious redirect
script/meta redirect patterns detected in page source
brand impersonation
The domain mcw-casino.biz uses a .biz TLD to impersonate or ride the brand of MCW Casino, which operates under mcw-casino.cam (as revealed in the Cloudflare challenge cZone field). The .biz variant is a common typosquat/brand-impersonation pattern targeting users of the legitimate .cam domain. (location: metadata.json: domain=mcw-casino.biz; page.html: cZone='mcw-casino.cam')
malicious redirect
The Cloudflare challenge script reveals cZone set to 'mcw-casino.cam', indicating that successful challenge completion will redirect or route the user to the mcw-casino.cam domain. The .biz domain acts as an intermediary/redirect layer, a common technique to funnel traffic through a lookalike domain before landing on the actual gambling site, potentially stripping referral context or injecting tracking. (location: page.html and page-text.txt: window._cf_chl_opt cZone='mcw-casino.cam')
social engineering
The page uses a Cloudflare-branded interstitial ('Just a moment...') that prompts users to enable JavaScript and cookies to continue. This creates a false sense of legitimacy by mimicking a standard Cloudflare security check, lowering user guard before reaching the actual gambling site content. (location: page.html: <title>Just a moment...</title>, noscript challenge text)
hidden content
The page sets meta robots to 'noindex,nofollow', intentionally hiding itself from search engine crawlers and security scanners. This is atypical for a legitimate casino landing page and is consistent with evasion of automated threat detection systems. (location: page.html: <meta name='robots' content='noindex,nofollow'>)
curl https://api.brin.sh/domain/mcw-casino.bizCommon questions teams ask before deciding whether to use this domain in agent workflows.
mcw-casino.biz currently scores 49/100 with a suspicious verdict and medium confidence. The goal is to protect agents from high-risk context before they act on it. Treat this as a decision signal: higher scores suggest lower observed risk, while lower scores mean you should add review or block this domain.
Use the score as a policy threshold: 80–100 is safe, 50–79 is caution, 20–49 is suspicious, and 0–19 is dangerous. Teams often auto-allow safe, require human review for caution/suspicious, and block dangerous.
brin evaluates four dimensions: identity (source trust), behavior (runtime patterns), content (malicious instructions), and graph (relationship risk). Analysis runs in tiers: static signals, deterministic pattern checks, then AI semantic analysis when needed.
Identity checks source trust, behavior checks unusual runtime patterns, content checks for malicious instructions, and graph checks risky relationships to other entities. Looking at sub-scores helps you understand why an entity passed or failed.
brin performs risk assessments on external context before it reaches an AI agent. It scores that context for threats like prompt injection, hijacking, credential harvesting, and supply chain attacks, so teams can decide whether to block, review, or proceed safely.
No. A safe verdict means no significant risk signals were detected in this scan. It is not a formal guarantee; assessments are automated and point-in-time, so combine scores with your own controls and periodic re-checks.
Re-check before high-impact actions such as installs, upgrades, connecting MCP servers, executing remote code, or granting secrets. Use the API in CI or runtime gates so decisions are based on the latest scan.
Learn more in threat detection docs, how scoring works, and the API overview.
Assessments are automated and may contain errors. Findings are risk indicators, not confirmed threats. This is a point-in-time assessment; security posture can change.
integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.