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
brand impersonation
The domain xvideos4.com serves content branded as 'XVIDEOS.COM' / 'XVideos.com', including the official XVIDEOS logo, title 'Free Porn Videos - XVIDEOS.COM', and identical site structure. The legitimate domain is xvideos.com; xvideos4.com is a typosquat/impersonation domain presenting itself as the authentic brand. (location: page.html:4-5, page.html:46, metadata.json domain field)
malicious redirect
A video listing embeds a shortened URL (https://is.gd/RNyBAm) directly in the video title and href path, instructing users to 'copy-paste the URL' to reach 'full HD video'. This is a classic redirect lure using a URL shortener to obscure the final destination, which could lead to phishing, malware, or credential-harvesting pages. (location: page.html:268-274, page-text.txt:84)
social engineering
The video title containing the is.gd redirect is written in Japanese and uses persuasive language encouraging users to copy-paste the shortened URL for 'full HD video', a social engineering tactic designed to lure users off-platform to an unknown destination. (location: page.html:274, page-text.txt:84)
prompt injection
The domain xvideos4.com impersonates xvideos.com and serves a session_token embedded in the page's JavaScript configuration object (window.xv.conf). This token ('d6fb4eddb3dfe71f4YF84M9NjmY8q2hkf3A5EsGtj82wpX0njxusbCOzy1SP5k8Exy-Fr2NID86hRzOwmZgC2v6_Q059NCXWy0PW0NoVDyiiejIhTjMTpKeYU-xTbzX7useDwNinFY6K8afzfxWJ7ZkMPPZZnw5iC0k28JopMa8cerIgSaXZa4uYD3VofXwBkkBbrKb5yp6W_p_d') is exposed to any agent or scraper visiting this impersonation domain and could be used to hijack or replay sessions against the legitimate xvideos.com infrastructure. (location: page.html:32 (window.xv.conf.dyn.session_token))
curl https://api.brin.sh/domain/xvideos4.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
xvideos4.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.