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 'sharepoint-mil.us' directly impersonates Microsoft SharePoint by incorporating the 'sharepoint' brand name into a .us TLD domain with 'mil' appended to falsely suggest a U.S. military or government affiliation. This is a classic brand impersonation tactic targeting both Microsoft and U.S. government/military branding simultaneously. (location: domain: sharepoint-mil.us)
phishing
The domain combines 'sharepoint' (a widely-used Microsoft enterprise product) with 'mil' (suggesting U.S. military) under a .us TLD. This combination is a high-confidence phishing indicator designed to deceive military or government personnel into trusting the site as a legitimate SharePoint instance. (location: domain: sharepoint-mil.us)
credential harvesting
SharePoint impersonation sites are commonly deployed as credential harvesting pages, presenting fake Microsoft 365 / SharePoint login forms to capture usernames and passwords. The TLS connection failure (connected=false, cert_valid=false) means the site may not even serve HTTPS properly, consistent with a hastily deployed phishing kit. (location: domain: sharepoint-mil.us, TLS metadata)
social engineering
The domain name deliberately pairs 'sharepoint' with 'mil' to social-engineer users — particularly U.S. military or DoD-affiliated personnel — into believing the URL is an authorized government SharePoint portal. This false sense of institutional authority is a social engineering technique to lower user suspicion. (location: domain: sharepoint-mil.us)
malicious redirect
TLS connection failed entirely (connected=false), which is anomalous for a live site. The domain may be inactive, parked, or serving content only under specific conditions (e.g., redirecting only certain user agents or geolocations), a common evasion technique to avoid detection by automated scanners while still targeting real victims. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
curl https://api.brin.sh/domain/sharepoint-mil.usCommon questions teams ask before deciding whether to use this domain in agent workflows.
sharepoint-mil.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.