context safety score
A score of 46/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
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
Third-party script loaded from tobaltoyon.com (https://tobaltoyon.com/act/files/micro.tag.min.js?z=5752451&sw=/sw-check-permissions.js) with a service worker parameter (/sw-check-permissions.js). This domain is unrelated to the site's stated purpose and is known to be associated with push notification spam, unwanted redirects, and ad fraud. The service worker registration can persist malicious behavior even after the user leaves the page. (location: page.html:75)
hidden content
Yandex Metrika tracking pixel loaded via a noscript tag with the image positioned off-screen (left:-9999px) to silently track users who have JavaScript disabled. While Yandex analytics itself is not inherently malicious, its use on an Indian lottery results site (with no apparent Russian audience) is anomalous and the off-screen placement conceals it from casual inspection. (location: page.html:374)
social engineering
The site impersonates or closely mimics the official Nagaland State Lottery results service using the .one TLD rather than a government domain (.gov.in or nagaland.gov.in). It presents official-looking prize tables, government contact details, and authoritative lottery schedules to build trust, potentially directing users to purchase tickets through unverified 'online vendors' or third-party channels rather than official government sources. (location: page.html:290-292, page-text.txt:137-139)
brand impersonation
The domain lotterysambad.one mimics the well-known 'Lottery Sambad' brand (official results publication) using a non-official TLD. The site presents itself as the authoritative source for Nagaland State Lottery results, replicating official prize structures and timetables, without being affiliated with the Government of Nagaland. This could mislead users into trusting the site as an official government resource. (location: metadata.json, page.html:9, page.html:17)
curl https://api.brin.sh/domain/lotterysambad.oneCommon questions teams ask before deciding whether to use this domain in agent workflows.
lotterysambad.one currently scores 46/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.