context safety score
A score of 38/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
cloaking
Page conditionally redirects based on referrer or user-agent
cloaking
Page loads content in transparent or zero-size iframe overlay
obfuscated code
Multiple heavily obfuscated JavaScript blocks present in the page using character-code shifting, decodeURI with encoded strings, and runtime string reconstruction. These scripts load external ad network JavaScript from third-party domains (guidepaparazzisurface.com, acquiredeceasedundress.com, darnobedienceupscale.com) and are designed to obscure their true behavior from static analysis. (location: page.html lines 47-51 (inline script block), lines 3073-3093 (footer spots scripts))
malicious redirect
External script loaded from '//guidepaparazzisurface.com/bn.js' via an obfuscated inline script block. The domain name is suspicious (random-looking compound noun) and is consistent with malvertising or traffic-redirect networks used to redirect users to unwanted destinations. The script is loaded with data-cfasync='false' to bypass Cloudflare security scanning. (location: page.html line 50)
malicious redirect
Footer ad spot scripts dynamically load JavaScript from '//acquiredeceasedundress.com/bn.js' and '//darnobedienceupscale.com/bn.js'. Both domain names follow a pattern consistent with known malvertising/redirect networks. These scripts are invoked via obfuscated loaders with zone IDs and callback functions, hiding their ultimate redirect targets. (location: page.html lines 3076-3093)
social engineering
A prominently styled animated button labeled 'AI Jerk Off' links to 'https://s.8jfbt5va3r.com/v1/d.php?z=1508' — a shortened/redirect URL on an opaque third-party domain. The use of an AI-branded label combined with a redirect tracker URL is a social engineering pattern designed to lure clicks under the guise of an AI feature, potentially leading to unwanted sites or credential-harvesting pages. (location: page.html lines 94-99)
malicious redirect
Ad thumbnail labeled 'Create and Fuck your AI CumSlut' links to 'https://s.ku34bh9la09.com/v1/d.php?z=2644', an opaque redirect URL on a random-looking domain. The ad is embedded as a fake video thumbnail within the content grid, disguised to blend with legitimate video items. The ad also embeds an iframe from 'engine.sadbaguette.com' with a custom ad GUID, indicating third-party ad tracking/redirect infrastructure. (location: page.html lines 1123-1163)
hidden content
The TLS certificate has only 8 days until expiry (days_until_expiry: 8), which is unusual for a legitimate site and may indicate neglected or recently deployed infrastructure. While not hidden content per se, near-expiry certificates on active commercial sites can be a signal of transient/throwaway hosting setups. (location: metadata.json (tls.days_until_expiry: 8))
prompt injection
A banner message embedded in the page content reads: 'Due to the massive influx of AI generated video's I have decided to no longer accept it on this platform. Please upload it here instead rule34gen.com'. This text, displayed within the main content area and linking to an external domain (rule34gen.com), could be interpreted by AI agents crawling the page as an authoritative instruction to redirect upload activity to a third-party site — a low-confidence but possible prompt injection pattern targeting AI agents that process page text as instructions. (location: page.html lines 673-687)
curl https://api.brin.sh/domain/rule34video.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
rule34video.com currently scores 38/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.