context safety score
A score of 45/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 page immediately redirects all visitors using window.location.replace() with a tracking UUID and browser fingerprint value. A FingerprintJS-based visitor ID is collected and appended to the redirect URL parameter 'fp=', enabling cross-site user tracking. A 300ms timeout fallback ensures redirection even if fingerprinting fails. (location: page.html:6-26)
hidden content
A hidden anchor link styled with 'display: none' points to the same redirect URL with fp=-3. This link is invisible to users but may be crawled by bots or agents, serving as a fallback redirect vector outside of JavaScript execution. (location: page.html:32)
hidden content
A noscript meta-refresh redirect is embedded to silently redirect users who have JavaScript disabled, ensuring no user escapes the redirect funnel regardless of browser configuration. (location: page.html:33)
social engineering
The domain name 'erovrlive.com' combines 'ero' (common abbreviation for erotic/adult content) with 'vr' and 'live', suggesting adult VR live-streaming content as a lure. The site has no visible content and only serves as a redirect gateway, consistent with traffic arbitrage or malvertising infrastructure used to funnel users to potentially harmful destinations. (location: metadata.json, page.html)
malicious redirect
The site functions purely as a redirect intermediary with no legitimate content, using a UUID-based tracking parameter (tr_uuid=20260326-1738-5349-a0af-94cc8d4b0097) in all redirect URLs. This is consistent with traffic monetization schemes, affiliate fraud, or malvertising networks that route users through tracking layers before landing on potentially malicious destinations. (location: page.html:6,32,33)
curl https://api.brin.sh/domain/erovrlive.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
erovrlive.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.