context safety score
A score of 47/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
ZoomInfo Websights script uses obfuscated string construction via base64-encoded atob() calls combined with character-shifting arithmetic to dynamically build both a property name and script source URL, obscuring the actual endpoint being loaded from static analysis. (location: page.html:2219, page-text.txt:1355)
hidden content
A 1x1 pixel invisible iframe injected by Cloudflare's challenge platform script is created with style position:absolute, top:0, left:0, border:none, visibility:hidden. While this is a known Cloudflare bot-detection mechanism, the pattern of injecting hidden iframes via obfuscated inline scripts is a technique also used maliciously. (location: page.html:2260)
hidden content
Multiple 1x1 pixel tracking pixels with display:none are present: a Facebook Pixel noscript fallback image, two LinkedIn Insight Tag pixels (one standard collection pixel and one conversion pixel). These are standard ad-tracking pixels but represent hidden data exfiltration to third-party ad networks. (location: page.html:470-472, page.html:2201-2204)
obfuscated code
Google Analytics is loaded twice in the page head (duplicate script blocks at lines 420-427 and 807-815), and the BounceX/Wunderkind behavioral tracking tag is also duplicated (lines 433-440 and 821-828). Duplicate script injection can be a sign of template injection or content injection, though here it appears to be a WordPress theme configuration error. (location: page.html:420-428, page.html:807-816, page.html:433-440, page.html:821-828)
curl https://api.brin.sh/domain/dealeron.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
dealeron.com currently scores 47/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.