context safety score
A score of 46/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
The page at 78winc3.com renders a near-perfect replica of a Cloudflare block/challenge page, including Cloudflare branding, logo references, Ray ID, and footer links. The actual domain being accessed is 78winc3.com, but the page claims to be blocking access to 'nxguarder02.com', suggesting the Cloudflare UI is being spoofed to lend legitimacy to a deceptive site or to manipulate automated agents into trusting the page as a security checkpoint. (location: page.html:7, page.html:37, page.html:76)
social engineering
The page instructs users to 'email the site owner' with details about what they were doing, effectively soliciting behavioral and contextual information from visitors under the guise of resolving a security block. This is a social engineering vector to harvest information about the user's actions and intent. (location: page.html:60-62, page-text.txt:29-31)
malicious redirect
The scanned URL is 78winc3.com, but the Cloudflare block page references a completely different domain 'nxguarder02.com' as the site being protected. This domain mismatch strongly suggests the page is part of a redirect or cloaking chain, where the true destination or ownership is obscured behind a fake security interstitial. (location: page.html:37, metadata.json)
prompt injection
The page structure mimics an authoritative security gateway (Cloudflare), which could cause AI agents or automated scanners to treat the page as a trusted infrastructure response rather than potentially malicious content. The 'noindex, nofollow' robots meta tag combined with Cloudflare branding impersonation may be intended to suppress security tool analysis and manipulate agent decision-making about the site's trustworthiness. (location: page.html:11, page.html:7)
hidden content
The IP address 34.96.45.56 is present in the HTML in a hidden span element (class='hidden') that is only revealed on user click. While this pattern is standard in genuine Cloudflare pages, in the context of a spoofed page it represents obfuscated infrastructure information. The 'noindex, nofollow' meta tag also suppresses crawling to hide the page from security indexing. (location: page.html:70-74, page.html:11)
curl https://api.brin.sh/domain/78winc3.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
78winc3.com currently scores 46/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.