context safety score
A score of 39/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
encoded payload
suspicious base64-like blobs detected in page content
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
Domain 'lotus365exch.win' uses a .win TLD combined with the 'lotus365' brand name, impersonating Lotus365, a known online gambling/exchange betting platform. The use of a non-standard TLD (.win) with a recognizable brand name is a classic brand impersonation pattern used to deceive users into believing they are on the legitimate site. (location: metadata.json: domain field / URL https://lotus365exch.win)
hidden content
Commented-out IP harvesting script found in HTML source: a JSONP call to https://api.ipify.org with a callback that writes the visitor's public IP to the document. Though currently commented out, its presence indicates prior or potential future use for covert IP address collection and user tracking/profiling. (location: page-hidden.txt lines 7-13 / page.html lines 22-28)
hidden content
Commented-out Facebook Meta Pixel tracking code (Pixel ID: 1949390595505532) found in HTML source. Though disabled, it was previously used for covert user behavior tracking and audience profiling via Facebook's ad network, without visible disclosure to users. (location: page-hidden.txt lines 14-30 / page.html lines 30-44)
hidden content
Page visible text is entirely empty (whitespace only), while the page loads multiple JavaScript bundles (main.fdf52088928184f5a48c.js, vendor.js, custom.js, messages.js, socket.io.js). All content is rendered dynamically via an Angular app-root component, making static analysis of the actual site content and any embedded threats impossible without JavaScript execution. (location: page-text.txt (all lines blank) / page.html line 49: <app-root></app-root>)
social engineering
The site operates as an online gambling/betting exchange ('exch' in domain) under the Lotus365 brand. Online betting platforms operating on non-standard TLDs (.win) are frequently used to lure users with promises of gambling winnings, operating outside regulated jurisdictions, targeting users in regions where such platforms are restricted or illegal (e.g., India). (location: metadata.json: domain 'lotus365exch.win')
curl https://api.brin.sh/domain/lotus365exch.winCommon questions teams ask before deciding whether to use this domain in agent workflows.
lotus365exch.win currently scores 39/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.