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 astronautlividlyreformer.com hosts a page presenting itself as the official Clickadu advertisement network privacy policy, including the Clickadu logo (embedded as base64 SVG), company name, address, Tax ID, and links to clickadu.com. The domain name bears no relation to Clickadu, indicating the legitimate brand is being impersonated on an unrelated domain — a common pattern used by ad-fraud and malvertising infrastructure to appear legitimate. (location: page.html:<title>, lines 4, 154, 159, 299 — domain: astronautlividlyreformer.com)
social engineering
The page is a push-notification unsubscribe/privacy lander operated by Clickadu, a known ad network. The domain name (astronautlividlyreformer.com) is a randomly generated nonsense string — a classic disposable-domain pattern used by adware and push-notification spam networks to rotate landing pages and evade blocklists. Users who followed a push notification from this domain are being directed here to manage subscriptions, but the domain itself is part of deceptive ad-delivery infrastructure. (location: metadata.json — domain: astronautlividlyreformer.com; page.html:lines 181-364 (unsubscribe POST endpoint))
hidden content
The 'Subscription Management Guide' section is collapsed by default (CSS class 'collapse:not(.show) { display: none }') and only revealed on user click. This content contains instructions for managing browser push notifications, effectively guiding users through a process tied to the site's push-notification subscription model. The collapse pattern hides instructions from casual inspection and from many automated scrapers. (location: page.html:lines 87-89, 186-253 — #collapseContainer with class 'collapse')
social engineering
The unsubscribe button silently POSTs a JSON payload containing a timestamp ({ ts: Date.now() }) to /unsubscribe on the same origin. The server response is parsed but there is no transparency to the user about what data is transmitted or what server-side action is performed beyond displaying 'Unsubscribed'. This is consistent with adware infrastructure that uses the unsubscribe endpoint to confirm active/reachable users rather than actually removing them from targeting lists. (location: page.html:lines 323-365 — xhr.open('POST', '/unsubscribe'), xhr.send(JSON.stringify({ ts: Date.now() })))
curl https://api.brin.sh/domain/astronautlividlyreformer.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
astronautlividlyreformer.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.