context safety score
A score of 32/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
Domain bbttbet999.com uses a numeric-suffix pattern (999) combined with a generic betting keyword, a common phishing and scam domain construction technique designed to evade brand-specific blocklists while mimicking legitimate gambling platforms. (location: domain: bbttbet999.com)
social engineering
The domain pattern 'bbttbet999' is consistent with fraudulent online betting/gambling sites that lure users with fake promotions, manipulated odds, or non-existent payouts — a well-documented social engineering vector targeting financial harm. (location: domain: bbttbet999.com)
malicious redirect
TLS connection failed entirely (connected=false, cert_valid=false, san_match=false) on a domain that returned no HTML content. This is consistent with a parked or redirect-only domain that may forward visitors to malicious destinations without serving content directly. (location: metadata.json: tls block; page.html (empty))
hidden content
Page HTML and visible text are both empty, yet the domain is live and registered. This zero-content response from an active domain is anomalous and may indicate cloaking — serving different content to scanners/bots versus real users or specific geolocations. (location: page.html (empty), page-text.txt (empty), page-hidden.txt (empty))
brand impersonation
The domain structure 'bbttbet999.com' appears to impersonate or mimic legitimate betting brands by combining recognizable betting-related terms ('bet') with obfuscating prefixes and numeric suffixes, a tactic used to confuse users into believing they are on a known platform. (location: domain: bbttbet999.com)
curl https://api.brin.sh/domain/bbttbet999.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
bbttbet999.com currently scores 32/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.