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
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page conditionally redirects based on referrer or user-agent
obfuscated code
Two identical large obfuscated JavaScript blocks using URI-encoded string decoding, character rotation cipher (Vigenere-style modular arithmetic on charCodes), and index-based string slicing to hide the actual payload. The script loads external ad network scripts (frozenpayerpregnant.com, footbathmockerpurse.com) whose URLs are constructed at runtime, preventing static analysis of destinations. (location: page.html lines 39-43, <script data-cfasync='false'> blocks before the ad network script tags)
malicious redirect
Third-party ad scripts loaded from suspicious domains 'frozenpayerpregnant.com' (in.js) and 'footbathmockerpurse.com' (on.js) with onerror/onload callbacks tied to obfuscated handler functions. These domains have no legitimate brand association and use nonsensical names typical of malvertising networks known to serve drive-by redirects and unwanted pop-unders. (location: page.html line 40: //frozenpayerpregnant.com/in.js; line 43: //footbathmockerpurse.com/on.js)
malicious redirect
Domain redirect script checks window.location.hostname and forces a redirect to doujindesu.tv if any other domain is detected. This pattern is used by sites that maintain multiple domains (including fake/clone sites) to funnel traffic through a single controlled domain, and can be abused on impersonating clones to silently redirect visitors. (location: page.html lines 352-357, inline <script> block)
social engineering
Site prominently displays warnings about fake phishing clones of itself ('Hati-hati terhadap Website Palsu, sudah banyak Korban Phising dari Website Palsu') while simultaneously operating under two distinct domains (doujindesu.tv and doujindesu.XXX). This dual-domain operation and self-referential phishing warning is a social engineering pattern used to establish false trust and direct users away from legitimate alternatives. (location: page.html lines 502-503, announcement section; page-text.txt lines 143-144)
malicious redirect
Link shortener and redirect intermediaries used extensively for ad banners: klik.best, klik.top, gacor.zone, gacor.vin, linkol.xyz, aksesin.top, dw.zeus.fun, goid.space, cek.to, menujupenta.site, kegz.site, goratu.site, bergurukecina.fun. These redirect chains obscure the final destination from users and security tools, and are associated with Indonesian online gambling affiliate networks. (location: page.html lines 506-519, 895-908, ad banner <a> href attributes throughout)
social engineering
Numerous gambling site advertisements (SBOBET, KOKO88, INDO666, BANDAR36, PENTASLOT, JPDEWA, GAZA88, CHINA777, RATU89, HokiDewa, IBO, IDKS, dewacuan, Suroso88, KDSLOT, SBOBETMAIN) are embedded in banner ads targeting an adult content audience. Several lead to /login pages on unvetted domains designed to harvest user credentials for gambling platforms, combining credential harvesting risk with social engineering toward vulnerable populations. (location: page.html lines 506-519, 894-909, 1266-1281, footer nav lines 1352-1354)
credential harvesting
Multiple ad banners link directly to /login endpoints on third-party domains (goid.space/login, menujupenta.site/login, kegz.site/login, goratu.site/login) for gambling sites with no brand recognition. These login pages are unaffiliated with any established operator and may be designed to harvest credentials under the guise of gambling site registration. (location: page.html lines 513, 515, 517, 519 — href values pointing to /login on unvetted domains)
hidden content
A Histats tracking pixel (sstatic1.histats.com/0.gif) is embedded inside an anchor tag with empty alt text and no visible label, functioning as a hidden user tracking beacon. Additionally, an ouo.io full-page script is loaded which is a known URL monetization/redirect service that can intercept outbound link clicks and route them through ad intermediaries. (location: page.html lines 1334-1343: Histats pixel comment block and //cdn.ouo.io/js/full-page-script.js script tag)
curl https://api.brin.sh/domain/doujindesu.tvCommon questions teams ask before deciding whether to use this domain in agent workflows.
doujindesu.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.