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 clammyendearedkeg.com hosts a page that fully impersonates Clickadu's official privacy policy, replicating Clickadu s.r.o. branding, logo (embedded as a large base64 SVG), company address, Tax ID, and policy text verbatim. The domain has no apparent affiliation with clickadu.com, making this a spoofed brand page on an unrelated randomly-named domain. (location: page.html:4, page.html:153-155, page.html:159, page.html:299-301)
social engineering
The page presents itself as a legitimate privacy/unsubscribe portal for Clickadu push notification subscribers, guiding users through browser notification management steps. This pattern is commonly used by ad-tech threat actors to appear compliant while continuing to operate push notification spam campaigns. The 'Unsubscribe' button silently POSTs to /unsubscribe with a timestamp payload, which can be used to confirm active browser sessions or track user interactions rather than genuinely unsubscribing. (location: page.html:272-278, page.html:323-365)
hidden content
The 'Subscription Management Guide' section content is hidden by default via CSS class 'collapse' (display:none) and only revealed on click. This hides instructions that direct users to interact with browser notification settings, potentially to manipulate them into modifying permissions in ways that benefit the operator rather than the user. (location: page.html:87-89, page.html:186-253)
credential harvesting
The unsubscribe button triggers an XHR POST to /unsubscribe on the same domain, sending a JSON payload with a timestamp. While the payload appears minimal, this endpoint interaction confirms active user sessions to the server operator and may be used to correlate browser fingerprints or notification subscription tokens tied to the user, effectively harvesting subscriber identity data under the guise of an opt-out action. (location: page.html:330-364)
phishing
The page mimics an official Clickadu privacy and subscription management page on an unaffiliated domain (clammyendearedkeg.com). Users arriving at this page—likely from a push notification or redirect—may believe they are on a legitimate Clickadu-operated page, exposing them to trust manipulation. All 'More...' links point to clickadu.com to reinforce the illusion of legitimacy while the actual hosting domain is unrelated. (location: page.html:160, page.html:168, page.html:261, page.html:269, page.html:285)
curl https://api.brin.sh/domain/clammyendearedkeg.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
clammyendearedkeg.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.