context safety score
A score of 47/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
malicious redirect
The page is served under domain mcwthomo.com but the Cloudflare challenge configuration sets cZone to 'mcw-casino.cam', revealing the true destination domain is a gambling/casino site distinct from the presenting domain. This domain mismatch indicates the registrant domain is acting as a redirector or cloaking layer for mcw-casino.cam. (location: page.html / page-text.txt: window._cf_chl_opt cZone='mcw-casino.cam')
brand impersonation
The domain mcwthomo.com (97 days old) presents a Cloudflare interstitial challenge page while its Cloudflare zone is configured as 'mcw-casino.cam'. The use of a generic-looking domain to front a casino brand is consistent with typosquat or cloaking infrastructure used to evade brand-abuse detection. (location: metadata.json: domain=mcwthomo.com; page.html: cZone='mcw-casino.cam')
social engineering
The page instructs users to 'Enable JavaScript and cookies to continue', a standard-looking browser challenge that normalizes enabling JavaScript and cookies in a context where the true destination (mcw-casino.cam) differs from the presented domain. This lowers user defenses before redirecting to the actual site. (location: page.html: noscript block, span#challenge-error-text)
hidden content
The page carries a meta refresh tag set to 360 seconds and uses a full-page Cloudflare managed challenge with obfuscated token parameters (cH, md, mdrd fields containing long opaque base64-like strings). While consistent with legitimate Cloudflare bot management, the combination with domain mismatch makes these tokens a potential cloaking mechanism hiding the redirect target from automated scanners. (location: page.html: <meta http-equiv='refresh' content='360'>; _cf_chl_opt md/mdrd fields)
curl https://api.brin.sh/domain/mcwthomo.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
mcwthomo.com currently scores 47/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.