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
obfuscated code
Two identical inline <script data-cfasync='false'> blocks use a multi-layer obfuscation technique: a Caesar-cipher-like character rotation applied to a packed string, followed by array-index splitting and dynamic function construction. The decoded payload resolves external hostnames at runtime, making static analysis of the final URLs/actions impossible. The same obfuscated blob appears both in the page body and in the footer. (location: page.html:1349 and page.html:1406)
malicious redirect
An ad script is loaded from //clammyendearedkeg.com/bn.js with data-cfasync='false' (bypasses Cloudflare's rocket-loader scrubbing). The domain 'clammyendearedkeg.com' is a randomly-named, non-descriptive hostname typical of malvertising networks and is not a known legitimate ad provider. It injects content into multiple <div data-cl-spot='1882206'> slots. (location: page.html:1380)
malicious redirect
A second third-party script is loaded from //badlandlispyippee.com/on.js with data-cfasync='false'. The domain 'badlandlispyippee.com' is a nonsense-named hostname characteristic of malvertising or click-fraud networks. It is loaded asynchronously with onerror/onload callbacks wired to an obfuscated function fvbzwsm(15). (location: page.html:1407)
hidden content
Multiple <link rel='preconnect'> tags silently pre-establish TCP/TLS connections to five external domains before any user interaction: assignlabor.com, eventsbands.com, counter.yadro.ru, unseenreport.com, and addresseepaper.com. Several of these (assignlabor.com, eventsbands.com, unseenreport.com, addresseepaper.com) are non-descriptive domains with no apparent legitimate relationship to the site, consistent with covert tracking or resource-staging infrastructure. (location: page.html:4-9)
hidden content
A LiveInternet tracking pixel (counter.yadro.ru) is loaded via a dynamically constructed image src that exfiltrates the visitor's full URL, page title, referrer, screen resolution, and color depth to a Russian analytics service. The image element is initially rendered with no src (invisible) and the script injects it at runtime. (location: page.html:1410-1415)
social engineering
Multiple video titles use 'Leaked', 'Real', 'Viral', and 'Scandal' framing (e.g., 'Real incest tape!', 'Leaked Desi MMS!', 'Viral Desi MMS') to create a false impression of non-consensual, authentic recordings. This social-engineering pattern is used to drive clicks and engagement by exploiting voyeuristic appeal and the implied authenticity of real victims. (location: page.html:697-1340 (Top Rated section video titles))
obfuscated code
The obfuscated script blocks invoke a callback function named fvbzwsm() which is referenced in the onload and onerror handlers of the badlandlispyippee.com script. This function is defined inside the obfuscated payload and its behavior cannot be determined without runtime execution, masking potentially malicious post-load actions. (location: page.html:1407)
curl https://api.brin.sh/domain/area51.pornCommon questions teams ask before deciding whether to use this domain in agent workflows.
area51.porn 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.