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
Domain 'ln-dc-msedge.net' mimics Microsoft Edge ('msedge') by incorporating the official Microsoft Edge browser process name into a non-Microsoft controlled domain. The prefix 'ln-dc-' is a common obfuscation pattern used to evade detection while the core brand term 'msedge' references Microsoft's browser engine, likely to deceive users or automated systems into trusting the domain. (location: domain: ln-dc-msedge.net)
phishing
The domain 'ln-dc-msedge.net' uses a .net TLD combined with a subdomain-style prefix ('ln-dc-') appended to the Microsoft Edge brand name ('msedge'). This construction is a hallmark phishing pattern: impersonating a trusted brand under a lookalike domain to harvest credentials or redirect victims. TLS is not connected and the certificate is invalid, consistent with a hastily stood-up phishing infrastructure. (location: domain: ln-dc-msedge.net, metadata.json tls.connected=false, tls.cert_valid=false)
credential harvesting
The combination of a Microsoft brand-impersonating domain ('msedge'), failed TLS (no valid certificate), and a non-Microsoft registrar with unknown hosting reputation are strong indicators of a credential-harvesting site. Such infrastructure is routinely used to serve fake Microsoft login pages to capture usernames and passwords. (location: domain: ln-dc-msedge.net, metadata.json tls fields)
malicious redirect
The domain 'ln-dc-msedge.net' shows no page content (empty HTML and text), which is consistent with a redirect-only or cloaked endpoint. Sites that return empty content to scanners but serve malicious redirects to real browsers are a common evasion technique, routing victims to phishing or malware pages while appearing benign to automated analysis. (location: page.html (empty), page-text.txt (empty))
curl https://api.brin.sh/domain/ln-dc-msedge.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
ln-dc-msedge.net 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.