context safety score
A score of 48/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 'c-msedge.net' impersonates Microsoft Edge (msedge.net is the legitimate Microsoft Edge CDN/service domain). The 'c-' prefix is a common typosquatting/subdomain spoofing pattern used to appear as a Microsoft property while operating on a distinct, unaffiliated domain. (location: domain: c-msedge.net)
phishing
Domain 'c-msedge.net' mimics a Microsoft Edge infrastructure domain. Combined with a failed TLS connection (connected=false, cert_valid=false), this pattern is consistent with a phishing or credential harvesting setup that may intercept users expecting legitimate Microsoft services. (location: domain: c-msedge.net, TLS status in metadata.json)
malicious redirect
The site returned empty page content (page.html and page-text.txt are empty) despite the domain being reachable enough for metadata collection. This blank-page pattern is commonly used in redirect chains where the real payload is delivered after a bot/agent check or JavaScript redirect that was not captured. (location: page.html, page-text.txt)
hidden content
TLS connection failed (connected=false, cert_valid=false) for a domain impersonating a Microsoft infrastructure service. The absence of a valid TLS certificate on a domain designed to look like a trusted Microsoft endpoint is suspicious and may indicate an interception proxy, a staging phishing kit, or an infrastructure component designed to operate over insecure channels to facilitate credential theft. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
curl https://api.brin.sh/domain/c-msedge.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
c-msedge.net currently scores 48/100 with a suspicious verdict and medium 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.