context safety score
A score of 41/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 buffooncountabletreble.com hosts a page that fully impersonates Clickadu's official privacy policy, replicating Clickadu s.r.o. branding, logo (embedded as base64 SVG), corporate address, Tax ID, and privacy policy text verbatim. The domain is unrelated to clickadu.com, creating a deceptive facade of legitimacy for what is a push-notification spam/ad network operation. (location: page.html:4, page.html:153-155, page.html:299-301)
social engineering
The page is designed to appear as a legitimate Clickadu privacy/unsubscribe portal. It guides users through push notification subscription management while operating from a nonsense lookalike domain (buffooncountabletreble.com). The 'Unsubscribe' button POSTs to /unsubscribe on this third-party domain rather than clickadu.com, potentially harvesting device/browser fingerprint data or confirming active push notification subscriptions to the ad network operator. (location: page.html:272-277, page.html:330-364)
credential harvesting
The 'Unsubscribe' button silently POSTs JSON data (including a timestamp) to /unsubscribe on the attacker-controlled domain buffooncountabletreble.com via XHR. While only {ts: Date.now()} is sent in the visible code, the endpoint on the rogue domain can correlate browser cookies, IP addresses, and push notification tokens to profile and confirm active subscribers for continued ad targeting or sale to third parties. (location: page.html:330-365)
hidden content
The logo image is embedded as a large base64-encoded SVG data URI (data:image/svg+xml;base64,...) inline in the HTML rather than served from clickadu.com. This obfuscates the full content of the image from casual inspection and is consistent with techniques used to hide secondary payloads or tracking pixels within seemingly innocuous image data. (location: page.html:154)
social engineering
The page presents a 'Subscription Management Guide' with step-by-step browser instructions ostensibly to help users unsubscribe from push notifications. This content is collapsed by default (hidden via CSS class 'collapse') and is only shown on user interaction, reducing scrutiny. The guide reinforces the legitimacy narrative while the real purpose of the domain is push-notification ad delivery infrastructure for Clickadu's network. (location: page.html:181-253, page.html:87-89)
curl https://api.brin.sh/domain/buffooncountabletreble.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
buffooncountabletreble.com currently scores 41/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.