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 'spov-dc-msedge.net' impersonates Microsoft Edge ('msedge') by embedding the official Microsoft Edge browser identifier in a non-Microsoft domain. The 'spov-dc-' prefix disguises the impersonation while 'msedge.net' closely mimics the legitimate Microsoft Edge infrastructure (microsoftedge.com / msedge.net used by Microsoft). This is a classic typosquatting/brand impersonation pattern targeting users and AI agents that may trust 'msedge' as a Microsoft-affiliated domain. (location: domain: spov-dc-msedge.net)
phishing
The domain 'spov-dc-msedge.net' exhibits strong phishing indicators: it impersonates a Microsoft product (Edge/msedge), TLS connection failed entirely (connected=false, cert_valid=false), the page returned no content, and hosting reputation is unknown. This combination — brand-spoofed domain with no valid TLS and empty page content — is consistent with a phishing lure or credential harvesting staging site that may only serve malicious content to targeted victims or specific user-agent/referrer combinations. (location: domain: spov-dc-msedge.net, TLS: connected=false)
credential harvesting
The site spoofs Microsoft Edge infrastructure ('msedge') without valid TLS, no content rendered publicly, and unknown hosting reputation. This pattern is consistent with a credential harvesting operation designed to capture Microsoft account credentials under the guise of an Edge-related authentication or update page, served conditionally to targeted sessions. (location: domain: spov-dc-msedge.net, metadata.json tls.connected=false)
malicious redirect
The domain 'spov-dc-msedge.net' returned empty page content despite a connection attempt, while spoofing Microsoft Edge naming. Empty-page responses on brand-impersonating domains frequently indicate a redirect gateway that routes victims based on user-agent, geolocation, or referral headers — serving benign empty content to scanners while redirecting real targets to phishing or malware payloads. (location: domain: spov-dc-msedge.net, page.html: empty, page-text.txt: empty)
curl https://api.brin.sh/domain/spov-dc-msedge.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
spov-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.