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
brand impersonation
Domain 'microsoftapp.net' impersonates Microsoft by incorporating the 'microsoft' brand name into a non-Microsoft controlled domain. This is a classic typosquatting/brand impersonation pattern used to deceive users and AI agents into trusting the domain as an official Microsoft property. (location: domain: microsoftapp.net)
phishing
The domain 'microsoftapp.net' is a non-official domain mimicking Microsoft branding. Combined with a failed TLS connection (connected=false, cert_valid=false), this pattern is highly consistent with a phishing infrastructure setup targeting users seeking Microsoft services or applications. (location: domain: microsoftapp.net, TLS metadata)
credential harvesting
Domains impersonating Microsoft (microsoftapp.net) are frequently used to serve fake Microsoft login pages designed to harvest credentials (Microsoft account usernames, passwords, MFA tokens). The domain structure and branding impersonation strongly suggest this intent even with no page content returned. (location: domain: microsoftapp.net)
malicious redirect
The TLS connection failed (connected=false, cert_valid=false, san_match=false) yet the domain resolves and was scanned. This may indicate the site redirects HTTP traffic or operates on non-standard infrastructure designed to evade detection while still serving malicious content to targeted victims. (location: metadata.json: tls fields)
social engineering
The domain name 'microsoftapp.net' is crafted to create a false sense of legitimacy by combining a globally trusted brand name ('microsoft') with a generic functional term ('app'), a well-known social engineering technique to lower user suspicion and induce interaction with malicious content. (location: domain: microsoftapp.net)
curl https://api.brin.sh/domain/microsoftapp.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
microsoftapp.net 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.