context safety score
A score of 27/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
credential harvesting
credential form posts to an off-domain endpoint (may be legitimate SSO/OAuth)
credential harvesting
The page is hosted on videw.online but all form actions (signin and signup) POST credentials directly to https://vidoy.com/signin and https://vidoy.com/signup — a different domain. Users entering credentials on videw.online have their username/password/email sent to vidoy.com, which is a classic cross-domain credential harvesting pattern. (location: page.html:71 (signin form action), page.html:97 (signup form action))
brand impersonation
The site videw.online clones the visual identity, logo, CSS, and JS assets of vidoy.com (loading stylesheets and scripts directly from https://vidoy.com/assets/). The page title says 'Vidoy' and the footer copyright reads '© 2012 - 2025 Vidoy.com', while the actual domain is videw.online — a typosquat/lookalike domain designed to impersonate vidoy.com. (location: page.html:7 (title), page.html:28-29 (asset links from vidoy.com), page.html:165 (footer copyright))
phishing
videw.online is a lookalike domain for vidoy.com (transposition of 'e' and 'w'), presenting a fully functional login and registration page that visually mimics the legitimate vidoy.com site. The domain was likely registered to intercept users who mistype or are directed to videw.online instead of vidoy.com. (location: metadata.json (domain: videw.online), page.html:71,97)
malicious redirect
Form submissions for both sign-in and sign-up redirect the browser to vidoy.com after credential submission (via form action URLs). This creates a seamless phishing flow: user submits credentials to vidoy.com from the fake domain, and may be transparently forwarded, masking the credential theft. Additionally, all CSS/JS assets are loaded cross-origin from vidoy.com, meaning the operator of videw.online does not control the full page behavior. (location: page.html:71 (action=https://vidoy.com/signin), page.html:97 (action=https://vidoy.com/signup))
curl https://api.brin.sh/domain/videw.onlineCommon questions teams ask before deciding whether to use this domain in agent workflows.
videw.online currently scores 27/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.