context safety score
A score of 49/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
phishing
TLS connection failed (connected=false, cert_valid=false, san_match=false) on a gambling/financial platform that collects user credentials and payment information. Users cannot verify site authenticity, making this a high-risk credential harvesting vector. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
betwayafrica.com is a gambling site requiring account login and financial transactions, but TLS is not functioning (connected=false, cert_valid=false). Any credentials or payment data entered would be transmitted without verified encryption, exposing users to interception. (location: metadata.json: tls object)
brand impersonation
The domain betwayafrica.com uses the 'Betway' brand name with a regional suffix ('africa'). Betway is a well-known international gambling brand. This subdomain/regional variant pattern is commonly used in brand impersonation schemes to target African markets with a fraudulent lookalike site. The failed TLS certificate further suggests this may not be the legitimate Betway infrastructure. (location: metadata.json: domain=betwayafrica.com)
malicious redirect
The page HTML and page text are completely empty despite the domain resolving. This is consistent with a cloaking or redirect-based attack where content is served conditionally (e.g., only to real browsers, not crawlers), potentially redirecting users to phishing or malware pages while appearing blank to automated scanners. (location: page.html (empty), page-text.txt (empty))
hidden content
All content files (page.html, page-text.txt, page-hidden.txt) are empty, yet the domain is active. This absence of scrapable content suggests aggressive cloaking techniques that hide actual page content from security scanners, a known evasion tactic used by malicious sites. (location: page.html, page-text.txt, page-hidden.txt (all empty))
curl https://api.brin.sh/domain/betwayafrica.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
betwayafrica.com currently scores 49/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.