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 'msidentity.net' closely mimics Microsoft's identity platform (login.microsoftonline.com / Microsoft Identity Platform). The name 'msidentity' directly appropriates Microsoft's 'MS' abbreviation and 'identity' branding, a classic typosquatting/brand impersonation pattern used to deceive users and AI agents into trusting the domain as a legitimate Microsoft authentication endpoint. (location: domain: msidentity.net)
credential harvesting
A domain impersonating Microsoft's identity/authentication platform (msidentity.net) is a high-confidence credential harvesting vector. Such domains are routinely used to host fake Microsoft login pages that capture usernames, passwords, and MFA tokens. The TLS failure (connected=false, cert_valid=false) suggests the site may be down, newly stood up, or actively evading inspection. (location: domain: msidentity.net, metadata.json tls block)
phishing
The combination of a Microsoft identity brand-impersonating domain name, failed TLS connection, and unknown hosting reputation is a strong phishing indicator. Users or automated agents directed to msidentity.net would likely believe they are interacting with a legitimate Microsoft authentication service. (location: domain: msidentity.net, metadata.json)
malicious redirect
Domains impersonating Microsoft identity services are frequently used as redirect hops in phishing chains, forwarding victims through the fake domain to a credential-capture page or back to a legitimate-looking page after theft. The empty page content is consistent with a redirect-only or cloaked page that serves different content to real visitors versus scanners. (location: domain: msidentity.net, page.html (empty))
hidden content
The page.html, page-text.txt, and page-hidden.txt files are all empty despite the domain being reachable enough for metadata to be collected. This is consistent with cloaking — serving no content to crawlers/scanners while delivering malicious content to targeted human visitors or specific user-agents. (location: page.html, page-text.txt, page-hidden.txt (all empty))
curl https://api.brin.sh/domain/msidentity.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
msidentity.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.