context safety score
A score of 46/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
script/meta redirect patterns detected in page source
malicious redirect
The entire page consists of a single JavaScript redirect using location.replace() to forward visitors to https://vidooy.com/videy.php. The use of location.replace() removes the original URL from browser history, preventing back-navigation — a technique commonly used in phishing chains and malware delivery flows. The target path '/videy.php' is a PHP script with no visible context. (location: page.html:2)
brand impersonation
The domain 'vidooy.com' closely resembles 'videy.com', a legitimate short video hosting platform, with a single character substitution ('oo' vs 'e'). This typosquatting pattern is consistent with brand impersonation intended to intercept users who mistype the legitimate domain. The redirect destination '/videy.php' reinforces this by referencing the legitimate brand name 'videy' in the path. (location: metadata.json, page.html:2)
hidden content
The page renders no visible content to users (page-text.txt is empty) and delivers only a silent JavaScript redirect. All functionality is hidden from casual inspection and from users without JavaScript. This evasion technique conceals the page's true purpose from both users and basic crawlers. (location: page.html, page-text.txt)
phishing
Combined indicators suggest phishing infrastructure: 83-day-old domain with typosquatted name mimicking 'videy.com', a blank page with only a silent JavaScript redirect to a PHP endpoint, and no legitimate content. This pattern is consistent with a phishing staging or relay page designed to funnel victims toward a credential-harvesting or malware-delivery endpoint. (location: metadata.json, page.html:2)
curl https://api.brin.sh/domain/vidooy.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
vidooy.com currently scores 46/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.