context safety score
A score of 34/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
cloaking
Page conditionally redirects based on referrer or user-agent
social engineering
The site betswiz.in is an online betting/gambling platform targeting users with the .in (India) TLD. The domain name mimics a legitimate-sounding branded betting service ('BetsWiz'), which combined with the gambling vertical is a common pattern for platforms that may operate outside regulatory frameworks and engage in deceptive acquisition tactics. (location: metadata.json: domain=betswiz.in)
malicious redirect
JavaScript on the page implements an aggressive mobile redirect that fires on page load AND repeats every 1000ms (1 second) via setInterval. This polling redirect loop forcibly and repeatedly pushes mobile users to /m/, preventing users from staying on the main page and potentially used to serve different content to different user agents — a common cloaking technique. (location: page.html: lines 16-33, setInterval redirect loop)
hidden content
The page renders with body{display:none} in the inline CSS, meaning the entire page body is invisible on initial load. All visible content is deferred to JavaScript bundles (Angular SPA). This technique hides the true content from static crawlers and security scanners, allowing the site to serve different or malicious content dynamically while appearing empty to non-JS analysis tools. (location: page.html: line 41, inline style body{display:none})
hidden content
All page meta tags (title, og:title, og:description, meta description) are intentionally left blank/empty. This suppresses search engine indexing signals and content previews, which is atypical for a legitimate branded site and suggests deliberate obfuscation of the site's identity and purpose. (location: page.html: lines 6, 8, 9, 11 — empty title and meta tags)
curl https://api.brin.sh/domain/betswiz.inCommon questions teams ask before deciding whether to use this domain in agent workflows.
betswiz.in currently scores 34/100 with a suspicious verdict and low 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.