context safety score
A score of 40/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
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page conditionally redirects based on referrer or user-agent
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
A popunder script fires on any user click, opening a new window to 'https://cdn-linker.com/2befbe6e-9e96-41a7-afb5-0805e6660957' using a cookie-gated mechanism (cookie 'popundr', 2-hour TTL). The window is opened as 'about:blank' first and then navigated via window.location assignment to evade popup blockers. This is a classic drive-by redirect / popunder ad pattern that can deliver malware or unwanted content. (location: page.html:437-590 (inline script body, checkTarget/doOpen functions))
hidden content
A full promotional banner (topNotice div) with links to 'https://a.candyai.love/...' and a call-to-action 'CREATE and FUCK your own AI GIRLFRIEND / TRY FOR FREE' is fully implemented in HTML including JavaScript event handlers, but is wrapped in an HTML comment block, hiding it from rendering while preserving the code for potential uncommenting/activation. The content and destination URL are concealed from casual inspection. (location: page.html:591-695 / page-hidden.txt:4-105)
malicious redirect
An external JavaScript file is loaded from a non-canonical path: 'https://adultgamesworld.com/27fdc13c1e.js'. The filename is an obfuscated hex-like string with no descriptive name, consistent with fingerprinting or ad-injection scripts. Its content is unknown and not loaded from a recognized CDN or library path. (location: page.html:26)
malicious redirect
A hidden video/link overlay element ('#slideApple') with display:none is present at the bottom of the page. It contains an autoplay muted looping video element and a blank anchor tag ('#slideAppleLink') with no href, populated dynamically by '/vs.js?v=1'. This is a covert ad-injection or redirect mechanism driven by an external opaque script. (location: page.html:1103-1107)
social engineering
Sponsored content tiles are embedded inline in the game listing grid with only a small 'SPONSORED' or 'Sponsored' overlay badge, visually blending paid advertisements (linking to cdn-linker.com and animeapp.org) with organic game listings. This deceptive UI pattern misleads users into clicking ads they believe are content listings. (location: page.html:832-949 (sponsored-post divs))
malicious redirect
Ad iframes are loaded from 'https://candy.engine.adglare.net/' with 'allow="autoplay; fullscreen"' permissions. Adglare is a third-party ad server; granting fullscreen and autoplay to a third-party iframe creates a vector for misleading full-screen takeover ads or forced redirects originating from ad network content. (location: page.html:802-818 (showindesk and showinmob iframe elements))
curl https://api.brin.sh/domain/adultgamesworld.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
adultgamesworld.com currently scores 40/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.