context safety score
A score of 31/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 'msauth.net' closely mimics Microsoft's authentication infrastructure by combining 'ms' (Microsoft abbreviation) with 'auth' (authentication), designed to deceive users and AI agents into believing they are interacting with a legitimate Microsoft authentication endpoint (e.g., login.microsoftonline.com or msauth.microsoft.com). (location: domain: msauth.net)
phishing
The domain 'msauth.net' uses a .net TLD instead of .com or .microsoft.com to masquerade as a Microsoft authentication service. This is a classic phishing infrastructure pattern used to harvest Microsoft/Azure/Office 365 credentials from users tricked into visiting the domain. (location: domain: msauth.net)
credential harvesting
A domain impersonating Microsoft authentication ('msauth.net') with no valid TLS certificate (TLS connected=false, cert_valid=false) is a strong indicator of a credential harvesting operation. Legitimate Microsoft auth endpoints always use valid TLS. The absence of TLS suggests the site may intercept credentials without encryption or has been taken offline after credential collection activity. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
malicious redirect
The domain 'msauth.net' mimicking a Microsoft authentication endpoint may serve as a relay or redirect node in an OAuth/SSO phishing chain, forwarding victims to the real Microsoft login after credential capture to avoid suspicion. Empty page content may indicate the site is dormant, blocking crawlers, or only active under specific referral/victim conditions. (location: domain: msauth.net; page.html: empty)
social engineering
The domain name 'msauth.net' is crafted to psychologically reassure victims that they are on a legitimate Microsoft authentication page. The combination of a plausible subdomain-like structure and 'auth' keyword exploits users' familiarity with Microsoft SSO flows, lowering their guard before credential submission. (location: domain: msauth.net)
curl https://api.brin.sh/domain/msauth.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
msauth.net currently scores 31/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.