context safety score
A score of 49/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
brand impersonation
The domain deputizepacifistwipe.com (357 days old, suspicious random-word name) hosts a page that fully impersonates Clickadu's official privacy policy, using Clickadu's logo (embedded as a base64 SVG), branding, and corporate identity (Clickadu s.r.o., Zenklova 32/28, Praha 8, Czech Republic, Tax ID 04066260) without being the legitimate clickadu.com domain. The page title explicitly states 'Operated by Clickadu Advertisement Network', mimicking official Clickadu infrastructure. (location: page.html:4, page.html:5 (favicon from clickadu.com), page.html:154 (base64 Clickadu logo), page.html:159)
social engineering
The page is a push-notification unsubscribe lure operated by an ad network on a throwaway random-word domain. It presents a fabricated 'Privacy Policy' and 'Subscription Management Guide' to appear legitimate and trustworthy, guiding users through browser notification settings—a common tactic used after tricking users into enabling push notifications via deceptive ad-network redirects. The 'Unsubscribe' button POSTs to /unsubscribe on the same suspicious domain, potentially confirming active browser/user identifiers to the operator. (location: page.html:181-364, page.html:272-278)
credential harvesting
The 'Unsubscribe' button silently POSTs JSON containing a timestamp (Date.now()) to /unsubscribe on the suspicious domain. While ostensibly an unsubscribe action, this confirms an active user session and browser fingerprint to the operator of this throwaway domain. The endpoint behavior is opaque and the domain has no established reputation, making silent data exfiltration likely. (location: page.html:330-364 (XHR POST to /unsubscribe with JSON payload))
hidden content
The 'Subscription Management Guide' section is hidden by default via CSS class 'collapse:not(.show) { display: none }' and only revealed on user click. This hides content from casual inspection and automated crawlers, a technique used to evade security scanners while still delivering the content to interactive users or agents that execute JavaScript. (location: page.html:87-89 (.collapse CSS rule), page.html:186 (collapseContainer div with class collapse))
curl https://api.brin.sh/domain/deputizepacifistwipe.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
deputizepacifistwipe.com currently scores 49/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.