context safety score
A score of 44/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
Domain melbet-312756.top uses a numeric suffix pattern (melbet-312756) to impersonate the legitimate Melbet gambling brand. The HTML explicitly references 'Melbet' in asset paths (e.g., /sys-static/sys-technical-pages-app-static/Desktop/Melbet/entry-83f4ab02f7.js) and CSS (non-embedded.css for Melbet), indicating deliberate brand cloning on a lookalike domain rather than the official melbet.com. (location: metadata.json:domain, page.html:1,4,5)
prompt injection
The server-side rendered data embeds a custom user-agent string 'brin-agent/1.0' in the userAgentSsr field and populates a blockingCookieValue ('eyJ0ZW1wbGF0ZSI6MSwicnVsZSI6MjJ9', base64 decoding to {"template":1,"rule":22}) targeting the scanning agent by name. The site is actively fingerprinting and responding to AI/automated agents with a BlockPage variant, suggesting the page serves different content to agents vs. real users to evade detection. (location: page.html:5, page-text.txt:1 (userAgentSsr, blockingCookieValue, mfc BlockPage))
hidden content
The page served to the scanner is a technical block/error page that conceals the actual site content from automated agents. The mfc array contains both 'ErrorPage' and 'BlockPage' variants, and the userBlockingInfo object confirms the agent was identified and blocked. Real users would see different (likely gambling or phishing) content, while scanners see a blank technical page — a classic cloaking technique. (location: page.html:5, page-text.txt:1 (mfc, userBlockingInfo, BlockPage variant))
malicious redirect
The page embeds a dynamic script loader that fetches a remote version.json from v3.traincdn.com before injecting scripts into the DOM. This CDN-based script injection pattern (Promise.race with fetch, then dynamic script tag appending) allows the remote CDN to deliver arbitrary JavaScript payloads to users without them appearing in the static HTML, enabling undetectable redirects or malicious code delivery. (location: page.html:1 (inline script, window.cdn loader, v3.traincdn.com))
social engineering
The domain melbet-312756.top mimics a legitimate gambling brand with a numeric identifier suffix, a common pattern used to lure users who mistype or follow affiliate/spam links. The site uses geo-blocking (geoCode: US, headerGeocode: US) and user-agent-based blocking to serve different experiences to different audiences, consistent with a fraudulent site that shows legitimate-appearing content to targeted victims while hiding it from security researchers. (location: metadata.json:domain, page.html:5 (userBlockingInfo geoCode, userAgentSsr))
curl https://api.brin.sh/domain/melbet-312756.topCommon questions teams ask before deciding whether to use this domain in agent workflows.
melbet-312756.top currently scores 44/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.