context safety score
A score of 49/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
hidden content
The page delegates multiple Client Hints headers (sec-ch-ua, sec-ch-ua-bitness, sec-ch-ua-arch, sec-ch-ua-model, sec-ch-ua-platform, sec-ch-ua-platform-version, sec-ch-ua-full-version, sec-ch-ua-full-version-list, sec-ch-ua-mobile) to the third-party domain tsyndicate.com via a meta http-equiv delegate-ch directive. This silently forwards detailed browser fingerprinting data to an external ad/tracking network without user awareness. (location: page.html line 1, <meta http-equiv="delegate-ch"> delegating to https://tsyndicate.com)
social engineering
The site promotes free access to copyrighted adult content with persuasive marketing language ('✓ All is FREE!!!', '✓ 100% Uncensored JAV', '✓ Fastest Streaming Options') to encourage users to engage with a piracy platform. This social engineering is designed to lower user guard and drive repeated visits and ad impressions on a site monetized through aggressive ad networks. (location: page.html line 59-66, page-text.txt lines 49-54)
malicious redirect
The footer contains a dense network of outbound links to third-party adult and aggregator sites (fcjav.com, bestjapanesepornsites.com, javgg.club, javup.org, porncrash.com, hornyjav.com, theporndude.com, arcjav.com, roshy.tv, sextb.net, sexasia.net, missav.li, etc.) without rel="nofollow" on all links. Several links use target="_blank" without rel="noopener noreferrer" consistently, and the site includes a Telegram channel link (t.me/ilovejavclub) that could redirect users to uncontrolled external content delivery channels. (location: page.html line 59, footer partner links section)
hidden content
A Cloudflare challenge script is inlined at the bottom of the page with an obfuscated payload in a data attribute: window.__CF$cv$params={r:'9d70e8d1fc150008',t:'MTc3MjYyNzYwNw=='}. While this is standard Cloudflare bot protection, the base64-encoded token and dynamic script injection pattern could be used to fingerprint or challenge AI agents and automated crawlers differently from human browsers. (location: page-text.txt line 58, inline Cloudflare script block)
hidden content
The page uses pervasive lazy-loading with placeholder SVG data URIs (data:image/svg+xml,%3Csvg...) for all thumbnail images. While this is a standard performance technique, it means the true image content is only revealed to JavaScript-executing clients, potentially hiding content from non-JS scanners and AI agents that do not execute JavaScript. (location: page.html lines 11-50, multiple <img> tags with data:image/svg+xml src and data-lazy-src attributes)
curl https://api.brin.sh/domain/javgg.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
javgg.net currently scores 49/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.