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
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
js obfuscation
Obfuscated document.write with encoded content
malicious redirect
The canonical URL and og:url meta tags on klevu.com point to athoscommerce.com instead of klevu.com. The page actively redirects users to a different domain (athoscommerce.com) via prominent CTAs and structural metadata. While this appears to be a legitimate rebrand (Klevu acquired by Athos Commerce), the pattern of a well-known domain funneling all traffic to a different domain is a redirect risk worth flagging — especially since the destination domain is not the scanned domain. (location: page.html:17 (<link rel='canonical' href='https://athoscommerce.com' />), page.html:21 (og:url), page.html:494 (Visit Athos Commerce CTA))
brand impersonation
The page presents itself as 'Klevu' (klevu.com) but the canonical URL, og:url, structured data WebPage url, and primary CTA all point to athoscommerce.com. The favicon files served from klevu.com have been replaced with athos_commerce_fav assets. This mismatch between the scanned domain identity and the rendered brand identity could confuse users or AI agents that rely on canonical signals to verify site identity. (location: page.html:342-345 (favicon links with cropped-athos_commerce_fav), page.html:17 (canonical), page.html:487 ('Klevu is now Athos Commerce' heading))
social engineering
The page uses urgency-free but directive language to push all visitors toward athoscommerce.com, framing the entire klevu.com domain as a deprecated entity. All primary action buttons (Contact Us, Get A Demo, Privacy Policy) link to athoscommerce.com rather than klevu.com subpages, effectively using the trusted klevu.com domain as a trust bridge to drive traffic to an external domain. (location: page.html:425 (Contact Us -> athoscommerce.com/contact-us-klevu/), page.html:459 (Get A Demo -> athoscommerce.com/request-demo-klevu/), page.html:564 (Privacy Policy -> athoscommerce.com/legal/))
curl https://api.brin.sh/domain/klevu.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
klevu.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.