context safety score
A score of 43/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
cloaking
Page loads content in transparent or zero-size iframe overlay
social engineering
Site self-describes as an '18-kin' (18+ prohibited) content aggregator publishing non-consensual sexual content, rape videos, leaked intimate images, and content sexualizing minors (e.g., '10代美少女' posts, '女子小学生' posts). Titles explicitly reference leaked/non-consensual material to lure users into clicking through, a classic shock-content social engineering pattern. (location: page.html:200-606, page-text.txt:115-499)
hidden content
Multiple ad scripts use randomized weighted selection via document.write() to inject different third-party ad tags at runtime (smac-ad.com and bance.jp), making it impossible to statically audit which ad payload will be delivered. One ad variant wraps ad HTML inside a hidden <textarea class='pcTag' style='display:none'> and extracts it via JS before writing to the document — a known technique for evading static content scanners. (location: page.html:648-662, page.html:1094-1207)
obfuscated code
Ad injection logic repeatedly uses document.write() with dynamically selected payloads from a weighted random array, combined with hidden textarea containers used as script stores. This pattern obscures the actual ad payloads from static analysis and can be used to deliver malicious scripts that bypass CSP and scanners. (location: page.html:1118-1133, page.html:1143-1159, page.html:1165-1182)
prompt injection
The page includes an HTML comment '<!--消去しないで下さい。-->' ('Do not delete') embedded in the body and footer sections, a minor but noted out-of-band instruction pattern. No explicit AI-targeting prompt injection text was found; however, the presence of a third-party script from yameyou.com (https://yameyou.com/load.js) loaded unconditionally in the <head> represents an unauditable remote code execution vector that could serve injected instructions to AI agents crawling the page. (location: page.html:88, page.html:1064, page.html:1088)
malicious redirect
An external script is loaded from https://yameyou.com/load.js unconditionally in the page <head>. This domain is unrelated to the site's own infrastructure and could serve redirect or drive-by-download payloads to visitors including automated agents. The koteiLinkSystem() function calls (KLS-13, KLS-16, KLS-17) render dynamic link content in empty divs without any visible source URL, which could inject arbitrary redirect links not visible during static analysis. (location: page.html:88, page.html:135-137, page.html:636-638, page.html:870-872)
social engineering
Multiple post titles reference minors in sexual contexts (e.g., '10代美少女を肉便器に' — sexualizing teenage girls; '女子小学生、10個上のヤンキーと付き合った結果レ●プよりヤバい事される' — elementary school girl subjected to abuse; '幼女がレ●プされてる現場' — child rape scene; 'このアイドル女子高生（16歳）、2年後男達のセ○クスの道具にされてしまう' — idol high school girl age 16 sexualized). This constitutes CSAM-adjacent social engineering content designed to drive clicks to pages potentially hosting illegal material. (location: page.html:533-547, page.html:816-822, page.html:826-831, page.html:964-965, page-text.txt:443, page-text.txt:731, page-text.txt:741, page-text.txt:875)
curl https://api.brin.sh/domain/po-kaki-to.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
po-kaki-to.com currently scores 43/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.