context safety score
A score of 34/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 'microsoftonline-p.com' is a typosquat/impersonation of the legitimate Microsoft authentication domain 'microsoftonline.com'. The addition of '-p' is a classic deceptive modification used to mimic Microsoft's identity and authentication platform (Microsoft Online / Azure AD / Entra ID) to deceive users and AI agents into treating it as a trusted Microsoft property. (location: domain: microsoftonline-p.com)
phishing
The domain 'microsoftonline-p.com' impersonates Microsoft's login portal (login.microsoftonline.com), which is a primary target for credential phishing campaigns. This pattern is consistent with adversary-in-the-middle or credential harvesting phishing infrastructure targeting Microsoft 365, Azure, and enterprise SSO users. (location: domain: microsoftonline-p.com)
credential harvesting
Domains spoofing 'microsoftonline.com' are overwhelmingly used to host fake Microsoft login pages that capture usernames, passwords, and MFA tokens. The TLS connection failure (connected=false, cert_valid=false) is consistent with a newly stood-up or dormant phishing page that may activate on demand. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
malicious redirect
The site returned no page content (page.html and page-text.txt are empty) despite the domain being active. This is consistent with a redirect-only phishing infrastructure or a page that only renders content to targeted victims (e.g., via geo-filtering, user-agent checks, or referrer-based activation), making static analysis evasion a likely deliberate design. (location: page.html (empty), page-text.txt (empty))
social engineering
The domain name 'microsoftonline-p.com' is designed to exploit user trust in the Microsoft brand. The '-p' suffix may be presented to victims as standing for 'portal', 'premium', or 'partner', lending false legitimacy and lowering suspicion during a social engineering attack targeting enterprise users or automated agents. (location: domain: microsoftonline-p.com)
curl https://api.brin.sh/domain/microsoftonline-p.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
microsoftonline-p.com currently scores 34/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.