context safety score
A score of 39/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 loads content in transparent or zero-size iframe overlay
malicious redirect
Navigation menu contains a tracked affiliate redirect link to Stripchat via go.rmhfrtnd.com with long obfuscated userId and sourceId parameters, routing users through an intermediary tracking/redirect domain before reaching the destination. The URL structure (go.rmhfrtnd.com/smartpop/...) is characteristic of traffic monetization networks that can chain redirects to malicious or deceptive destinations. (location: page.html:118 - <a href="https://go.rmhfrtnd.com/smartpop/213183bbf19adb525b60a6acedc6bc7f4f820d74dcff915eceec809898939c05?userId=...&sourceId=...">Stripchat</a>)
malicious redirect
Header banner ad loaded via iframe sourcing from go.mnaspm.com, another opaque redirect/ad-network domain with obfuscated userId and sourceId tracking tokens. The iframe loads external content with no sandbox restrictions, allowing the ad server to execute arbitrary JavaScript within the page context. (location: page.html:125 - <iframe src="https://go.mnaspm.com/smartpop/892ba35e3fed4f61bf21c650534ccc486d3eabe6e8e97a208c8faff41af86c66?userId=...&sourceId=headerbanner">)
malicious redirect
TrafficStar popunder ad network script loaded from cdn.tsyndicate.com with spot ID d4f4dbea65de4879aaf49cfee71ba4f6. PopUnder scripts are used to silently open new browser windows/tabs to arbitrary URLs without user consent, a common vector for delivering phishing pages, tech-support scam pages, and credential harvesting sites. (location: page.html:631 - <script src="//cdn.tsyndicate.com/sdk/v1/p.js" data-ts-spot="d4f4dbea65de4879aaf49cfee71ba4f6" ...>)
malicious redirect
TSVideoInstantMessage widget loaded from cdn.tsyndicate.com with spot ID d98765aa50374ad2b282f48ed70dcced. This TrafficStar product injects floating video ad units that can trigger popunder redirects on click, routing users to third-party destinations not controlled by the site operator. (location: page.html:634-646 - TSVideoInstantMessage({spot: "d98765aa50374ad2b282f48ed70dcced", ...}))
malicious redirect
JuicyAds popunder script loaded from js.juicyads.com with redirect target encoded as URL parameter pointing to juicyads.rocks. JuicyAds is an adult ad network known to serve popunder advertisements that redirect to potentially harmful pages including fake prize pages, tech-support scams, and subscription traps. (location: page.html:653 - <script src="https://js.juicyads.com/jp.php?c=34e4v233t254u4q2x26433d474&u=https%3A%2F%2Fwww.juicyads.rocks">)
social engineering
Site presents itself as hosting amateur/homemade content with real named individuals (e.g., Andrea Ceballos, Sondra Blust, Vanessa Bohorquez) in video titles, implying non-consensual or leaked intimate content. This pattern is used to attract users searching for specific individuals and can facilitate sextortion or credential harvesting via fake login walls. (location: page.html:349-458 - video title listings including named individuals)
hidden content
The age_check JavaScript variable is explicitly set to 0 (age_check=0), indicating the site has disabled its age verification gate. While not a direct threat, disabling age checks is a regulatory compliance violation and signals that the operator may be evading safeguards, consistent with low-quality or rogue adult site behavior. (location: page.html:605 - var age_check=0;)
curl https://api.brin.sh/domain/otubex.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
otubex.com currently scores 39/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.