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 'dnscloudflare.net' directly impersonates Cloudflare, a major internet infrastructure and security company, by combining 'dns' and 'cloudflare' into a lookalike domain. This is a classic brand impersonation pattern used to deceive users and AI agents into trusting the domain as legitimate Cloudflare infrastructure. (location: domain: dnscloudflare.net)
phishing
The domain 'dnscloudflare.net' is highly consistent with a phishing infrastructure domain. It mimics Cloudflare's DNS services (1.1.1.1, dns.cloudflare.com) to lure users or systems expecting legitimate Cloudflare DNS endpoints. The TLS connection failed entirely (connected=false, cert_valid=false), indicating the site is not serving a valid HTTPS certificate, which is atypical for any legitimate service claiming Cloudflare affiliation. (location: domain: dnscloudflare.net; TLS: connected=false, cert_valid=false)
credential harvesting
Domains impersonating Cloudflare DNS infrastructure are frequently used to harvest credentials by presenting fake Cloudflare login or verification pages. The combination of brand impersonation and failed TLS is a strong indicator of a credential harvesting setup, even though page content was not retrievable. (location: domain: dnscloudflare.net)
malicious redirect
The domain 'dnscloudflare.net' using a DNS-themed Cloudflare impersonation name is a known pattern for traffic interception and malicious redirect infrastructure. Such domains are used to redirect DNS queries or HTTP traffic through attacker-controlled endpoints, enabling man-in-the-middle attacks or redirecting victims to malicious payloads. (location: domain: dnscloudflare.net)
social engineering
The domain name itself is a social engineering vector: by combining 'dns' and 'cloudflare', it creates a false sense of legitimacy and technical authority. Users and automated agents encountering this domain may be deceived into interacting with it as if it were an official Cloudflare DNS service. (location: domain: dnscloudflare.net)
curl https://api.brin.sh/domain/dnscloudflare.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
dnscloudflare.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.