context safety score
A score of 41/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
The page is a replica of Microsoft Outlook Web Access (OWA) login page, including Microsoft copyright headers ('Copyright (c) 2011 Microsoft Corporation'), OWA-specific JS (flogon.js, OwaPage = ASP.auth_logon_aspx), OWA path references (/owa/auth/15.2.1544/), and the Outlook branding. This is served from cdatribe-nsn.gov, a tribal government domain, not a Microsoft domain. This constitutes full Microsoft/Outlook brand impersonation. (location: page.html:1-6, page.html:1330, page.html:1383)
credential harvesting
The page presents a login form with username and password fields that submits to /owa/auth.owa on the same domain (cdatribe-nsn.gov). The form collects credentials under the guise of Microsoft Outlook authentication. The destination hidden field points to https://cdatribe-nsn.gov/owa/ rather than any legitimate Microsoft infrastructure. (location: page.html:1330-1396)
phishing
A complete Microsoft OWA phishing page is hosted on cdatribe-nsn.gov. The page faithfully replicates the OWA 15.2.1544 login experience — including CSS, JavaScript, embedded base64 logo images, and Microsoft branding — to deceive users into submitting their Microsoft/Exchange credentials to a non-Microsoft server. (location: page.html:1-1403)
social engineering
The page uses legitimate-looking Microsoft Outlook UI patterns (blue sidebar, Microsoft logo, 'sign in' button, 'Show password' checkbox, cookie warning with Outlook branding) to create a high-trust environment that socially engineers users into believing they are interacting with a genuine Microsoft service. (location: page.html:1342-1395, page-text.txt:41-70)
hidden content
The pre-scan context flagged a hidden content ratio of 0.02 and 7 suspicious base64 blobs. Multiple large base64-encoded PNG images are embedded inline (data:image/png;base64,...) in the HTML body and sidebar, including what appears to be the Microsoft OWA and Outlook logos. These blobs serve as self-contained assets that bypass external resource detection and allow the phishing kit to render convincingly without any off-domain fetches. (location: page.html:1314-1315, page.html:1344-1345, page.html:1352, page.html:1371-1373)
malicious redirect
The pre-scan context flagged 2 redirects and 1 JS redirect pattern. The redir() function in flogon.js dynamically redirects users using window.navigate() or window.location assignment driven by the variable a_sLgn, which is not defined in the captured HTML. This open redirect mechanism could forward users to attacker-controlled URLs after credential submission. (location: page.html:787-898)
curl https://api.brin.sh/domain/cdatribe-nsn.govCommon questions teams ask before deciding whether to use this domain in agent workflows.
cdatribe-nsn.gov currently scores 41/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.