context safety score
A score of 27/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 trustvalueindia.com is only 94 days old with no established reputation. The name combines trust-signaling words ('trust', 'value') with a geographic identifier ('india'), a common pattern in phishing and financial fraud sites designed to appear legitimate to unsuspecting users. (location: metadata.json: domain, whois.domain_age_days=94)
social engineering
The domain name 'trustvalueindia.com' employs trust-inducing language ('trust', 'value') as a social engineering mechanism to lower user suspicion. This naming pattern is frequently used in investment scams, fake financial services, and fraudulent e-commerce sites targeting Indian users or those dealing with Indian markets. (location: metadata.json: domain=trustvalueindia.com)
phishing
TLS/SSL connection failed entirely (connected=false, cert_valid=false, san_match=false). A site presenting itself as a trust/value financial service with no valid TLS certificate is a strong phishing indicator — legitimate financial or trust services always maintain valid HTTPS. Users submitting credentials or financial data would do so over an insecure or non-functional connection. (location: metadata.json: tls.connected=false, tls.cert_valid=false, tls.san_match=false)
credential harvesting
Combination of a trust-themed domain name, very young domain age (94 days), unknown hosting reputation, and failed TLS certificate is consistent with credential harvesting infrastructure. Such sites are commonly stood up rapidly to collect credentials before being taken down. (location: metadata.json: tls, whois.domain_age_days=94, hosting.reputation=Unknown)
curl https://api.brin.sh/domain/trustvalueindia.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
trustvalueindia.com currently scores 27/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.