context safety score
A score of 26/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
phishing
1 deceptive links where visible host does not match destination host
cloaking
Page conditionally redirects based on referrer or user-agent
obfuscated code
A heavily obfuscated JavaScript block tagged '<!-- Pops -->' uses URI-encoded string decoding, character-rotation ciphering, and array slicing to conceal its payload and behavior. The script loads an external resource from 'alfalfaemployeeresource.com' and contains logic to detect browser/UA type, suggesting a pop-under or redirect ad network payload that evades static analysis. (location: page.html:367-369 (<!-- Pops --> script block))
malicious redirect
Script at '//alfalfaemployeeresource.com/on.js' is loaded asynchronously with 'data-cfasync=false' (bypasses Cloudflare protection) and is associated with the obfuscated pop-under script. The domain 'alfalfaemployeeresource.com' is a known pop/redirect ad network domain used to deliver unwanted redirects or malicious pop-unders to visitors. (location: page.html:369)
social engineering
Third-party ad network 'a.magsrv.com' (MagSrv) is injected via inline script with 'async' loading and a push-based AdProvider pattern. MagSrv is a known adult ad network frequently associated with deceptive ad creatives including fake virus warnings, fake download buttons, and forced redirects targeting unsuspecting users. (location: page.html:189-192, 293-295, 327-329)
hidden content
jQuery is loaded twice: once from the site's own CDN (jquery.min.js v3.7.1) and again from code.jquery.com (jquery-1.11.0.min.js, an outdated version). The second inclusion is loaded after the body open tag outside of the WordPress asset pipeline, suggesting it may have been injected separately to support the obfuscated pop script or other non-disclosed functionality. (location: page.html:43-44 and page.html:155-157)
curl https://api.brin.sh/domain/javmix.tvCommon questions teams ask before deciding whether to use this domain in agent workflows.
javmix.tv currently scores 26/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.