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
malicious redirect
JavaScript dynamically injects advertisement links via DOM manipulation using randomized selection among three external domains (dirtytoyz.com, videosxy.net, wildtempt.com). Links are created programmatically and appended to the page without user interaction, bypassing static content filters. The wildtempt.com link includes UTM tracking parameters (utm_source=zoofilialovers&utm_campaign=button) indicating coordinated traffic steering. (location: page.html:92-135, adv-12 script block)
malicious redirect
Multiple third-party ad network scripts loaded from external CDNs: cdn.portalspace.my/sdk/push_web (push notification SDK), udzpel.com (obfuscated base64-encoded script URL), cdn.popcash.net/show.js (popunder ad network), and media.skytraffix.net/js/code.min.js (Skytraffix popup ad network). These scripts can trigger unsolicited redirects, popunders, and push notification subscription prompts without user consent. (location: page.html:546-555)
obfuscated code
Script loaded from udzpel.com uses a base64-encoded filename: 'waWQiOjEwODYwMDIsInNpZCI6MTQxNTY4Nywid2lkIjo2ODY4ODYsInNyYyI6Mn0=eyJ.js'. This obfuscation technique is used to hide the script's purpose and parameters from static analysis tools, and is a common indicator of malicious ad injection or tracking infrastructure. (location: page.html:547)
obfuscated code
The Skytraffix popup script uses a data-cfasync=false attribute to bypass Cloudflare's async script deferral and directly binds popup behavior to all anchor tags, images, and content areas on the page via bindTo: ['a','img','.content-area']. This means any click anywhere on the page can trigger a redirect or popup through idzone 151995. (location: page.html:555)
social engineering
Page advertises content falsely labeled as 'real incest' (e.g., 'My Uncle can't get enough of me real incest', 'Real Incest Uncle Fucked me') which are fabricated claims designed to manipulate users into clicking and engaging with content under false pretenses. This is a social engineering tactic to drive engagement and ad revenue. (location: page.html:302-310, 472-480)
hidden content
One video entry (video ID 45886) uses only emoji characters (transgender flag emoji) as both title and alt text with no descriptive content, effectively hiding the video's actual content from text-based scanners, search engine indexing, and content moderation tools while still being visible to users. (location: page.html:352-360)
malicious redirect
A local /pop.js script is loaded in the page head before any other JavaScript, suggesting a popunder or redirect script that executes at page load before user interaction. The filename and placement are consistent with popunder ad network initialization. (location: page.html:32)
social engineering
The age_check variable in the page's inline JavaScript is set to 0 (disabled), meaning the site does not enforce any age verification despite hosting explicit adult content. This removes a legal and ethical barrier intended to prevent minors from accessing the content, and may be used to maximize traffic and ad impressions. (location: page.html:593)
curl https://api.brin.sh/domain/bestialitysextaboo.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
bestialitysextaboo.net 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.