context safety score
A score of 45/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 aviatorreproducesauciness.com (244 days old, randomly-generated name) serves a page titled 'Operated by Clickadu Advertisement Network' and displays full Clickadu s.r.o. branding, logo, privacy policy, and contact details. The domain has no apparent affiliation with Clickadu. This is a typosquat/impersonation page designed to appear as an official Clickadu property to lend legitimacy to push-notification subscription abuse. (location: page.html:<title> (line 4), logo img (line 154), company name and address (lines 159, 299))
social engineering
The page poses as a legitimate privacy/unsubscribe portal for the Clickadu ad network, using official-looking branding and policy language to build false trust. The 'Unsubscribe' button and 'Subscription Management Guide' section are designed to socially engineer users into believing they are on an authoritative opt-out page, when the domain is unrelated to Clickadu. This pattern is consistent with push-notification spam infrastructure that tricks users into interacting with the page. (location: page.html: Subscription Management Guide section (lines 181-253), Unsubscribe button (lines 272-277))
social engineering
The page provides step-by-step browser notification management instructions specifically for Chromium, coaching users on how push notification permissions work. This content is typical of pages that previously abused push notifications and now serve a fake unsubscribe/privacy page to appear compliant, while the actual subscription was driven by a different mechanism on the same domain. (location: page.html: lines 188-252, page-text.txt: lines 38-103)
hidden content
The 'Subscription Management Guide' section and its detailed instructions are hidden by default via CSS class 'collapse:not(.show) { display: none; }' and only revealed on button click. This content is not visible on page load, making it invisible to casual inspection and basic crawlers, while still being served to users who interact with the page. (location: page.html: lines 87-89 (CSS), line 186 (collapseContainer with class 'collapse'), JavaScript toggle logic lines 310-313)
curl https://api.brin.sh/domain/aviatorreproducesauciness.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
aviatorreproducesauciness.com currently scores 45/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.