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 eccentricsterilizevastness.com hosts a page that presents itself as an official Clickadu advertisement network privacy policy page, using Clickadu's logo (embedded as a base64 SVG), favicon (loaded directly from clickadu.com), company name, address, Tax ID, and branded content. This is a third-party domain impersonating Clickadu's identity without being clickadu.com itself. (location: page.html:4-5, page.html:153-154)
social engineering
The page mimics a legitimate ad-network privacy/unsubscribe portal to build false trust. It presents official-looking policy sections (Privacy Policy, Information Security, Children's Privacy) and an 'Unsubscribe' button on a domain unrelated to Clickadu, creating a deceptive environment designed to manipulate users into believing they are interacting with the real Clickadu service. (location: page.html:156-302)
phishing
An 'Unsubscribe' button triggers a POST XHR request to '/unsubscribe' on the fraudulent domain eccentricsterilizevastness.com. Users who believe they are on the legitimate Clickadu site may interact with this endpoint, potentially submitting browser fingerprint data (timestamp sent as payload) or being profiled. The endpoint is opaque and under attacker control. (location: page.html:272-277, page.html:323-365)
hidden content
The 'Subscription Management Guide' section is collapsed by default (CSS class 'collapse' with display:none) and only revealed via JavaScript toggle. This section contains instructions for managing browser push notification permissions — content that is invisible on page load and could serve to guide users through steps that benefit the site operator (e.g., re-subscribing or confirming notification permissions). (location: page.html:186-253)
social engineering
The page includes a 'Subscription Management Guide' section with step-by-step instructions ostensibly for unsubscribing from push notifications. This content is characteristic of pages operated by push-notification ad networks to handle user complaints while retaining as many subscribers as possible, and may be used to confuse or dissuade users from actually removing notification permissions. (location: page.html:181-253)
curl https://api.brin.sh/domain/eccentricsterilizevastness.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
eccentricsterilizevastness.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.