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
malicious redirect
script/meta redirect patterns detected in page source
brand impersonation
The scanned URL is zeasn.tv but the page fully presents as 'Whale TV' (whaletv.com), including logo, title, navigation, meta tags, and all content. The HTML explicitly references data-wf-domain='www.whaletv.com' and all canonical/alternate links point to whaletv.com. A visitor navigating to zeasn.tv would believe they are on the legitimate whaletv.com site, which constitutes brand impersonation regardless of whether zeasn.tv is an affiliated domain. (location: page.html:1 - <html data-wf-domain='www.whaletv.com'>, <title>Whale TV | Home</title>, all hreflang links pointing to whaletv.com)
malicious redirect
JavaScript on the page performs automatic client-side redirects based on browser language and localStorage preferences (window.location.href = replaceLocaleInPath(targetLocale)). While this is ostensibly a locale-switching feature, the redirect logic executes unconditionally on DOMContentLoaded and can redirect users to attacker-controlled locale subpaths if the localStorage value 'preferredLocale' is tampered with or pre-set. Combined with the domain mismatch (zeasn.tv serving whaletv.com content), this redirect mechanism could be abused to chain users to unintended destinations. (location: page.html:144-182, page-text.txt:100-138)
social engineering
The page contains a newsletter signup form soliciting user email addresses ('Stay up to date by subscribing to our newsletter!'). Given that the page is served from zeasn.tv while impersonating whaletv.com, any email addresses submitted could be harvested by the operator of zeasn.tv rather than the legitimate Whale TV organization. (location: page-text.txt:1 - 'Want to know more? Stay up to date by subscribing to our newsletter!')
curl https://api.brin.sh/domain/zeasn.tvCommon questions teams ask before deciding whether to use this domain in agent workflows.
zeasn.tv 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.