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
The domain 'msidentity.us' closely mimics Microsoft Identity services (Microsoft's identity platform is 'microsoft.com/identity' or 'identity.microsoft.com'). The 'ms' prefix combined with 'identity' is a well-known pattern used to impersonate Microsoft authentication/identity infrastructure, targeting users and AI agents that interact with Microsoft identity flows. (location: domain: msidentity.us)
phishing
TLS/HTTPS connection failed (connected=false, cert_valid=false) on a domain impersonating Microsoft Identity. A site mimicking a trusted identity provider but unable to establish a valid TLS connection is a strong indicator of a phishing or fraudulent infrastructure setup, possibly serving content over insecure channels or intercepting credentials. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
A domain spoofing 'Microsoft Identity' (msidentity.us) is a classic credential harvesting vector. Users or automated agents believing they are interacting with Microsoft's identity/authentication service may submit OAuth tokens, passwords, or session credentials to this adversary-controlled endpoint. (location: domain: msidentity.us)
malicious redirect
The .us TLD combined with a Microsoft-impersonating name (msidentity.us) and failed TLS suggests this domain may be used as a redirect hop in phishing chains — receiving traffic from typosquatting or malicious links and forwarding victims to credential capture pages. Empty page content is consistent with a redirect-only or conditional-serving infrastructure. (location: domain: msidentity.us; page.html: empty)
social engineering
The domain name 'msidentity.us' is constructed to appear as an official US-government or Microsoft identity authority. The combination of 'ms' (Microsoft abbreviation), 'identity' (identity platform keyword), and '.us' (US government/official TLD connotation) is a deliberate social engineering construct to establish false legitimacy with both human users and AI agents processing URLs. (location: domain: msidentity.us)
curl https://api.brin.sh/domain/msidentity.usCommon questions teams ask before deciding whether to use this domain in agent workflows.
msidentity.us 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.