context safety score
A score of 30/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
cloaking
Page checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The site nagalandstatelottery.in presents itself as the official Nagaland State Lottery website but is not the actual government-operated lottery. It uses government lottery branding, draws, and prize structures to appear authoritative while redirecting users to third-party affiliate and gambling sites. The footer disclaimer itself admits results are extracted from other sites. (location: page.html:169-170, page.html:781-784)
malicious redirect
A prominent 'REFRESH NOW' link in the main content area points to nagalandstatelotterysambad.com (a different domain), silently redirecting users who expect to stay on the current site. PDF download links for official lottery results also point to nagalandstatelotterysambad.com rather than the claimed official government source. (location: page.html:214, page.html:228, page.html:237, page.html:246)
social engineering
The page embeds multiple unrelated third-party gambling affiliate links (Norwegian online casinos, CS2 gambling sites, Aviator games, casino-utan-spelpaus.net, betting-utan-svensk-licens.net, pusulabet, damangame.fun, nodepositninja.com) inside content that appears to be a legitimate government lottery results page. These are injected under a 'Read more' expand/collapse section to partially obscure them from casual inspection. (location: page.html:752-766, page-text.txt:592-607)
hidden content
Gambling affiliate links and promotional content for pusulabet, CS2 gambling, Norwegian casinos, and casino-without-Spelpaus sites are concealed inside an expand/collapse 'Read more' section (div id='yrm-orODV' with visibility:hidden and height:0 by default). This content is hidden from the initial rendered view but present in the DOM, targeting both users who don't expand it and AI agents scraping page text. (location: page.html:296-299, page-text.txt:592-608)
social engineering
The page uses fabricated future dates (24.6.4044) mixed with real current dates (4.3.2026) throughout the content, creating confusion about result validity and urgency. This is a dark pattern to make stale or fake content appear current, manipulating users into trusting and revisiting the site. (location: page.html:339-354, page-text.txt:179-194)
brand impersonation
The navigation menu contains a link labeled 'KOL555 news media' pointing to https://www.kol555.com/Topic/6, which appears to be an unrelated gambling/betting platform. This link is presented alongside legitimate navigation items to lend it credibility by association with an apparent official lottery site. (location: page.html:187)
obfuscated code
The page includes custom base64 encode/decode functions (b2a, a2b, b64e, b64d) defined in inline script blocks. These are used by the ad-insertion plugin to encode/decode ad block data attributes (data-ai), obscuring the actual content being injected into the page from static analysis. (location: page.html:673-675, page-text.txt:673-675)
social engineering
The site claims to be the 'official website' of Nagaland State Lottery in the footer while simultaneously disclaiming accountability for result accuracy. It drives users to bookmark the site and check it daily for lottery results, building habitual traffic to a non-official affiliate site that monetizes through gambling referrals. (location: page.html:781, page-text.txt:621-624)
malicious redirect
Image assets for lottery result tables are loaded from nagalandstatelotterysambad.com (a separate domain), not from the site's own domain. This cross-domain asset loading from a different operator's domain indicates content laundering and could be used to serve dynamic or manipulated result images. (location: page.html:466, page.html:500, page.html:502)
hidden content
Extensive keyword stuffing with hundreds of repeated lottery search terms is embedded in the visible page content as standalone paragraph tags, designed to manipulate search engine rankings. While primarily an SEO manipulation technique, it also functions to attract users searching for official government lottery results to this non-official site. (location: page.html:397-424, page-text.txt:491-590)
curl https://api.brin.sh/domain/nagalandstatelottery.inCommon questions teams ask before deciding whether to use this domain in agent workflows.
nagalandstatelottery.in currently scores 30/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.