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
Domain 'azure-dns.net' mimics Microsoft Azure branding by combining the 'azure' brand name with 'dns.net', impersonating Microsoft's Azure cloud platform infrastructure services to deceive users or automated agents into trusting the domain. (location: domain: azure-dns.net)
phishing
The domain 'azure-dns.net' is a non-Microsoft domain impersonating Azure infrastructure. TLS is not connected and the certificate is invalid, which is consistent with a phishing or malicious infrastructure domain that failed to properly configure SSL, raising the risk that the site is designed to harvest credentials or redirect users under a false Azure identity. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
malicious redirect
The page returned no content (empty HTML and text) despite the domain being reachable enough to scan. This blank-page pattern is commonly used in redirect chains where the real malicious payload is delivered after an initial redirect or bot-detection gate, hiding the true destination from automated scanners. (location: page.html (empty), page-text.txt (empty))
hidden content
The .brin-context.md references a 'page-hidden.txt' for extracted hidden content, and while that file is also empty, the combination of a brand-impersonation domain, no TLS, and zero visible or hidden content is consistent with a cloaked page that serves different content to real users versus crawlers/scanners. (location: page-hidden.txt (empty), page.html (empty))
curl https://api.brin.sh/domain/azure-dns.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
azure-dns.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.