context safety score
A score of 36/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
social engineering
Site presents itself as a legitimate online betting and casino platform ('R777') targeting users in India, offering real-money gambling ('online casino games real money', 'Cricket ID', 'exchange games'). This type of site commonly operates outside regulatory frameworks and uses familiar branding to attract and deceive users into depositing money. (location: page.html: <title> and <meta name='description'>)
hidden content
Two identical hidden zero-dimension iframes loading Google Tag Manager (GTM-WWPHLVM) are embedded in <noscript> tags. Duplicate GTM iframes are unusual and may be used to track users who have JavaScript disabled, or as an obfuscation technique to normalize the presence of tracking infrastructure while concealing additional payloads loaded via GTM. (location: page.html: <noscript> blocks; page-text.txt line 1)
obfuscated code
A dynamically constructed script tag appends 'bundle.js' with a hardcoded timestamp parameter at runtime via inline JavaScript. The main application logic is deferred to an external bundle (main.b6ff43f5.js) that cannot be statically inspected. This pattern is used to defer and obscure the actual site functionality, making static analysis of credential harvesting or malicious redirects impossible without executing the JavaScript. (location: page.html: inline <script> block constructing bundle.js dynamically)
credential harvesting
The site is a real-money online gambling platform ('Cricket ID', betting, casino) that almost certainly requires user registration with personal details and payment/financial information. The fully JavaScript-rendered single-page application (SPA) with deferred bundle loading means all login, registration, and payment forms are loaded dynamically and cannot be statically audited for credential harvesting behavior. (location: page.html: <div id='root'> SPA shell; deferred JS bundles main.b6ff43f5.js and bundle.js)
curl https://api.brin.sh/domain/r777.usCommon questions teams ask before deciding whether to use this domain in agent workflows.
r777.us currently scores 36/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.