context safety score
A score of 48/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
cloaking
Page conditionally redirects based on referrer or user-agent
brand impersonation
The URL being scanned is evidon.com, but the page renders entirely as Crownpeak (crownpeak.com) — a different brand and domain. The HTML title, og:url, all internal links, logos, and content belong to crownpeak.com, not evidon.com. Visitors arriving at evidon.com are silently presented with Crownpeak branding with no indication they are on evidon.com. This constitutes domain-based brand impersonation or an undisclosed domain takeover/redirect serving a third-party brand's full identity. (location: page.html:5-9, metadata.json (domain: evidon.com vs page title/og:url: crownpeak.com))
malicious redirect
The scanned domain evidon.com is serving content entirely belonging to crownpeak.com without any disclosed relationship or redirect notice. All canonical links, hreflang tags, og:url, favicon, stylesheets, and scripts point to crownpeak.com. This indicates a silent domain substitution or hijack where evidon.com traffic is being funneled to display a completely different brand's content, a classic indicator of a malicious or unauthorized redirect/domain repurposing. (location: page.html:5-15 (og:url, hreflang, link tags all reference crownpeak.com while domain is evidon.com))
hidden content
The page loads a third-party script from c.evidon.com (https://c.evidon.com/dg/dg.js with companyid=4957) and dynamically appends multiple additional scripts including evidon-sitenotice-tag.js, country.js, and settingsV2.js. While Evidon is a consent management platform, the domain being scanned IS evidon.com, and the page is loading scripts from c.evidon.com referencing a specific companyid. This self-referential external script loading on a domain that is not presenting its own brand content warrants scrutiny for hidden tracking or data harvesting activity not visible to end users. (location: page.html:24-27 (script companyid=4957, src=https://c.evidon.com/dg/dg.js))
curl https://api.brin.sh/domain/evidon.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
evidon.com currently scores 48/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.