context safety score
A score of 47/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
malicious redirect
JavaScript hostname check redirects visitors to http://www.seselah.com if the hostname does not contain 'lah'. This is a conditional client-side redirect to an unrelated third-party domain using unencrypted HTTP, executed silently without user interaction. (location: page.html:547-550)
malicious redirect
A keyword link labeled 'AI手淫' (AI masturbation) points to https://s.zlink0.com/v1/d.php?z=5639862 via a tracked redirect shortener rather than an internal tag page. All other keyword links go to relative ./tag/ paths; this single entry is routed through an opaque external redirect service, suggesting an undisclosed affiliate or traffic-hijacking redirect. (location: page.html:119)
hidden content
A 1x1 pixel invisible iframe is injected into the DOM at position absolute top:0 left:0 with visibility:hidden. A script is then written into its document that loads Cloudflare challenge-platform JS. This pattern is used to silently fingerprint or challenge visitors inside a hidden frame without their awareness. (location: page.html:563)
hidden content
Ad-block detection div (#eZpvzakmotcB) is hidden with display:none and forcibly shown as a modal blocking the full page when an ad blocker is detected, preventing site use. While technically disclosed in visible text, the mechanism uses a hidden element revealed via JS to coerce users into disabling security tools. (location: page.html:504-524)
social engineering
Users are pressured to register or log in with the promise of removing intrusive pop-up ads ('覺得彈窗廣告很煩是嗎？注册/登录就可以無彈窗廣告觀看所有影片啦！'). This is a social engineering tactic that leverages deliberate ad annoyance to harvest user account registrations and credentials. (location: page.html:83-84)
credential harvesting
The site presents login (/login) and registration (/register) endpoints. Users are manipulated into creating accounts via ad-annoyance social engineering. The registration flow collects user credentials on an adult content site that loads multiple third-party ad scripts, increasing exposure risk. (location: page.html:57-58, 83)
curl https://api.brin.sh/domain/papalah.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
papalah.com currently scores 47/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.