context safety score
A score of 34/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
brand impersonation
Domain 'poolbinance.com' impersonates Binance, the major cryptocurrency exchange, by prepending 'pool' to the official 'binance.com' brand name. This is a classic typosquatting/combosquatting technique used to deceive users into believing they are interacting with a legitimate Binance service (e.g., a Binance mining pool). (location: domain: poolbinance.com)
phishing
The combination of a Binance brand-impersonating domain with a completely failed TLS connection (connected=false, cert_valid=false, san_match=false) is strongly indicative of a phishing infrastructure. Legitimate financial/crypto services always enforce valid TLS. The site may be down, behind a redirect, or actively serving phishing content intermittently. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
Cryptocurrency exchange impersonation sites targeting Binance users are a well-established credential harvesting vector. Users tricked into visiting poolbinance.com expecting a legitimate Binance pool service may submit login credentials, API keys, seed phrases, or wallet information to attacker-controlled infrastructure. (location: domain: poolbinance.com)
malicious redirect
TLS connection failure (connected=false) with a non-blocklisted domain of 2200 days age suggests the domain may be parked, redirecting, or intermittently serving malicious content. The inability to retrieve any page content (page.html and page-text.txt are empty) is consistent with a redirect chain or cloaking behavior that evades automated scanners while serving malicious pages to real users. (location: metadata.json: tls.connected=false; page.html: empty; page-text.txt: empty)
curl https://api.brin.sh/domain/poolbinance.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
poolbinance.com currently scores 34/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.