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 attirecideryeah.com hosts a page with the title 'Operated by Clickadu Advertisement Network' and displays Clickadu s.r.o. branding, logo, privacy policy, and contact details. The domain name bears no relation to Clickadu, suggesting the domain is impersonating or spoofing the Clickadu ad network brand to appear legitimate while operating under a deceptive domain. (location: page.html:<title> (line 4), logo img (line 154), body text throughout)
social engineering
The page is a push-notification unsubscribe/privacy page for an ad network (Clickadu) served from an unrelated domain (attirecideryeah.com). This pattern is commonly used by adware and malicious ad networks to establish a veneer of legitimacy: users who received unwanted push notifications are directed here to 'unsubscribe', normalizing the interaction and collecting behavioral signals. The domain name is a random-looking string unrelated to any legitimate business, a hallmark of throwaway adware infrastructure. (location: page.html: Subscription Management Guide section (lines 181-253), Unsubscribe button (lines 272-277))
social engineering
The page provides detailed step-by-step instructions for managing browser push notification permissions in Chromium, framed as a helpful 'Subscription Management Guide'. This content is characteristic of push-notification spam operations that use such guides to manage user complaints while continuing to serve intrusive ads, rather than actually helping users escape the notification subscription. (location: page.html: lines 181-253, page-text.txt: lines 31-103)
hidden content
The 'Subscription Management Guide' collapsible section (id='collapseContainer') is hidden by default via CSS class 'collapse' with display:none. This content is not visible on page load and requires a click interaction to reveal. While the content itself is benign instructions, the use of hidden collapsible sections can be used to conceal content from automated scanners while still serving it to users. (location: page.html: line 186, CSS lines 87-89 (.collapse:not(.show) { display: none; }))
brand impersonation
The favicon is loaded directly from clickadu.com (https://clickadu.com/favicon.ico), further reinforcing impersonation of the Clickadu brand on a domain entirely unrelated to Clickadu. This is consistent with domain squatting or affiliate fraud infrastructure that mimics legitimate ad network pages. (location: page.html: line 5 (<link rel='shortcut icon' href='https://clickadu.com/favicon.ico'>))
curl https://api.brin.sh/domain/attirecideryeah.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
attirecideryeah.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.