context safety score
A score of 47/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
social engineering
Site impersonates an official government lottery results portal for Nagaland State Lottery, Kerala Lottery, Sikkim, West Bengal, and Mizoram state lotteries. The domain 'lotterysambadresult.in' is an unofficial third-party site that presents itself as an authoritative source for government lottery results, potentially misleading users into trusting it as official. FAQ content asserting '100% real' and official government backing reinforces false authority. (location: page.html:332-588, metadata.json domain field)
malicious redirect
A third-party ad script is dynamically injected via obfuscated lazy-load JavaScript from the domain 'zk.strayerchordal.com' (path /tlI5pdO24JhG/37470). This domain is not a known reputable ad network and the path pattern (random alphanumeric string) is characteristic of malvertising infrastructure. The script is loaded asynchronously with data-cfasync='false' to bypass Cloudflare bot protection, and injected through dynamic DOM manipulation rather than a static script tag, which is a common technique used to evade security scanners. (location: page.html:282-307 (lazy-ad-container script block))
obfuscated code
Ad payload is encoded as a string inside a JavaScript variable ('adContent') and injected into the DOM at runtime via innerHTML and dynamic script creation. This technique hides the actual third-party script source ('//zk.strayerchordal.com/tlI5pdO24JhG/37470') from static analysis and CSP inspection. The use of data-cfasync='false' explicitly disables Cloudflare's script proxy, ensuring the external script runs directly without intermediary inspection. (location: page.html:283-306)
brand impersonation
The site uses official government lottery brand names (Nagaland State Lottery, Kerala Lottery, Sikkim State Lottery, Punjab State Lottery, Dear Lottery) extensively throughout content, meta tags, schema markup, and structured data to appear as the official government lottery portal. The actual official Nagaland lottery site is nagalandlotteries.nic.in (a government domain), not this .in commercial domain. Schema.org markup identifies the site itself as an authoritative publisher of these government-run lotteries. (location: page.html:7-198 (schema markup), page.html:332-578 (body content))
social engineering
The site encourages users to 'bookmark' the site and 'keep visiting' to check lottery results daily, creating habitual return visits to a site that serves third-party ad scripts of uncertain provenance. The FAQ section reinforces legitimacy ('100% real') to build trust. (location: page.html:333, page.html:577, page.html:586-588)
curl https://api.brin.sh/domain/lotterysambadresult.inCommon questions teams ask before deciding whether to use this domain in agent workflows.
lotterysambadresult.in 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.