context safety score
A score of 48/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
The domain melbet-596650.top uses a numeric suffix pattern (596650) appended to the 'Melbet' brand name — a classic typosquatting/impersonation technique used to mimic the legitimate Melbet gambling brand while evading exact-match domain detection. (location: metadata.json: domain field, page.html: Melbet references in CDN paths and app config)
social engineering
The server-side blocking logic actively fingerprints the scanning agent by its User-Agent ('brin-agent/1.0') and serves a sanitized BlockPage/ErrorPage variant instead of the real page content. The field userAgentSsr='brin-agent/1.0' confirms the site detected and responded differently to the scanner, concealing actual content from automated analysis. (location: page.html: window.serverData userBlockingInfo.userAgentSsr='brin-agent/1.0', mfc BlockPage/ErrorPage variants)
hidden content
The site employs user-agent-based cloaking: it detects the scanning agent and serves a blocked/error page with no real content, while real users likely see gambling/betting content. The blockingCookieValue (base64: eyJ0ZW1wbGF0ZSI6MSwicnVsZSI6MjJ9 = {"template":1,"rule":22}) encodes a blocking rule applied specifically to this request, confirming deliberate content concealment from crawlers and security tools. (location: page.html: window.serverData userBlockingInfo.blockingCookieValue, mfc array with BlockPage variant)
malicious redirect
The page loads its entire application dynamically from an external CDN (v3.traincdn.com) via JavaScript, with no static content rendered server-side. This pattern allows the CDN to serve arbitrary content — including redirects or malicious payloads — that would not be visible in the initial HTML response captured by scanners. (location: page.html: window.cdn cdnURL='https://v3.traincdn.com', script src entry-b808396380.js loaded from external CDN)
curl https://api.brin.sh/domain/melbet-596650.topCommon questions teams ask before deciding whether to use this domain in agent workflows.
melbet-596650.top currently scores 48/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.