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
brand impersonation
The site uses the domain 'doujin-freee.cc' (triple 'e') which is a typosquat-style variation of legitimate doujinshi platforms. The .cc TLD combined with the deliberate misspelling pattern is consistent with brand impersonation of established Japanese doujinshi sites such as doujin-free.com or similar. The site impersonates the aesthetic and content structure of legitimate platforms to attract users who mistype or are redirected. (location: domain: doujin-freee.cc, page title: 無料同人誌 同人フリー)
hidden content
A hidden 1x1 invisible iframe is injected into the document body via an inline script block at the bottom of the page. The iframe is positioned absolutely at top:0, left:0 with visibility:hidden and no border. Inside the iframe, a dynamically created script sets Cloudflare challenge parameters and loads '/cdn-cgi/challenge-platform/scripts/jsd/main.js'. While this is nominally a Cloudflare bot-detection mechanism, the pattern of injecting hidden iframes with dynamically constructed script payloads that execute cross-origin code is a technique also used for covert tracking, fingerprinting, and ad fraud. The iframe itself is invisible to users. (location: page.html:556, inline <script> block appending hidden iframe to document.body)
prompt injection
The page contains an 'アップロード' (upload) link at /up/ allowing user-contributed content submission. On a site serving AI-scraped or AI-indexed adult content, user-uploaded content could embed prompt injection payloads in titles, tags, or alt text that would be processed by AI agents crawling or summarizing the site. The tag and title fields are rendered directly into the HTML without visible sanitization hints, creating a surface for injecting instructions targeting AI content processors. (location: page.html:532, sidebar upload link: /up/)
social engineering
The site's description and branding ('完全無料でサクサク読める', 'ストレスフリー', 'every day updated') uses persuasive dark-pattern language to encourage repeated visits and engagement with pirated/unauthorized doujinshi content. The 'free and stress-free' framing is designed to lower user guard and normalize consumption of potentially illegal copyright-infringing material. The tag 'JS' (elementary school) appears multiple times alongside 'ロリ' (loli) tags with characters described in contexts suggesting minors, which may be used to socially engineer users into consuming CSAM-adjacent content. (location: page.html:6 (meta description), page-text.txt:189-191 (JS/ロリ content listings))
hidden content
The Cloudflare challenge script injects a base64-encoded timestamp parameter 't':'MTc3MjYyNzc1Mw==' (decodes to '1772627753') embedded inline in the hidden iframe script. This encoded parameter obfuscates the actual request fingerprinting data being sent to external infrastructure, preventing casual inspection of what telemetry is being collected from visitors. (location: page.html:556, window.__CF$cv$params t parameter (base64 encoded))
curl https://api.brin.sh/domain/doujin-freee.ccCommon questions teams ask before deciding whether to use this domain in agent workflows.
doujin-freee.cc 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.