context safety score
A score of 44/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
malicious redirect
TLS connection failed entirely (connected=false, cert_valid=false, san_match=false) for a site using the 'onestore.ms' domain. The .ms TLD combined with 'onestore' is a clear imitation of Microsoft's 'microsoft store' branding. A non-functional TLS certificate on a brand-impersonating domain is a strong indicator of a malicious or deceptive redirect site that may redirect victims after capturing credentials or clicks. (location: metadata.json: tls block)
brand impersonation
The domain 'onestore.ms' closely mimics Microsoft's brand. 'One Store' or 'Microsoft Store' is a well-known Microsoft product, and the .ms TLD (assigned to Montserrat but frequently used to spoof 'Microsoft') reinforces the impersonation. This pattern is commonly used in phishing campaigns targeting Microsoft account credentials. (location: metadata.json: domain=onestore.ms)
phishing
Combination of brand impersonation (Microsoft Store lookalike via 'onestore.ms'), failed TLS, and empty page content is consistent with a phishing infrastructure page — either a dormant phishing kit, a credential-harvesting landing page not yet activated, or a page that only renders content under specific conditions (e.g., after redirect with token parameters). The domain is 10590 days old (~29 years), which is anomalous and may indicate a hijacked or resurrected domain used to lend false legitimacy. (location: metadata.json, .brin-context.md)
hidden content
Page HTML and visible text are completely empty despite the domain being live enough to have metadata collected. This blank-page pattern can indicate cloaking — serving empty content to crawlers/scanners while delivering malicious content to targeted human visitors based on user-agent, referrer, or session tokens. (location: page.html (empty), page-text.txt (empty), page-hidden.txt (empty))
curl https://api.brin.sh/domain/onestore.msCommon questions teams ask before deciding whether to use this domain in agent workflows.
onestore.ms currently scores 44/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.