context safety score
A score of 41/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
Aggressive popunder/tabunder ad system via ExoClick (zone 4344962) and Clickadilla networks. On click of nearly any page element, a new tab/window is opened to a third-party ad destination. The 'mz' mode sets frequency_per_page to 999999 with frequency_interval_time of 0.001, meaning virtually unlimited popunders per session. (location: page.html:228-270, popOptions/secondPopOptions config blocks)
malicious redirect
Canonical tag points to desi-porn.tube (a different domain) while the page is served from desi-porn.xyz. The site also encodes API keys for multiple domains (desi-porn.tube, desi-porn.xyz, desiporn.tube) suggesting a coordinated multi-domain redirect/traffic funnel operation. (location: page.html:11 (canonical href), page.html:59-63 (vf_keys))
malicious redirect
Randomized hardlink destinations (_hlink1, _hlink2) are chosen at 50/50 probability and injected into the page as tab-links. Destinations include affiliate tracking links to go2cloud.org, ctwmsg.com (LiveJasmin/CutiesAI affiliate), and go.rmhfrtnd.com — all with embedded affiliate/tracking IDs. Users clicking page elements may be silently redirected to these URLs. (location: page.html:763-806, page-text.txt:725-765)
social engineering
Age-verification bypass: the script sets localStorage '_agv'=1 and cookie '_agev' when the 'promo' parameter equals 47201, or when the referrer is not Google and a promo/utm_content parameter is present — effectively bypassing age gates for traffic arriving via affiliate/promo links. This circumvents legal age-gating requirements. (location: page.html:69-77, page.html:107-118)
social engineering
Geo-targeted age lock for UK visitors (country_code=='gb') is silently bypassed for affiliate-sourced traffic. UK visitors arriving via promo/utm links skip the age verification modal entirely, circumventing a legal compliance control. (location: page.html:66 (isAgeLock logic))
hidden content
The page title tag is empty (<title></title>) and the Vue.js app renders all content client-side via <router-view>. No visible text content is present in the HTML body for crawlers or agents — the actual page content is entirely hidden behind JavaScript rendering, making static analysis of the content impossible. (location: page.html:4, page.html:859-876)
hidden content
The .__bai-overlay element is styled with z-index: 99999 !important, placing an invisible click-capture overlay above all page content. This intercepts user clicks and routes them to popunder/ad destinations without the user being aware they are clicking an ad layer. (location: page.html:837-840, bindSel array referencing .__bai-overlay)
hidden content
Client Hints delegation via meta http-equiv='delegate-ch' sends detailed browser fingerprinting data (ua-bitness, ua-arch, ua-model, ua-platform, ua-platform-version, ua-full-version-list, ua-mobile) to tsyndicate.com on every request, enabling covert device fingerprinting beyond standard analytics. (location: page.html:31)
social engineering
A time-limited promotional button ('FULL VIDEO HERE') active until 2026-03-31 redirects to fhgte.com with utm tracking, and a promobar also points to fhgte.com — these use urgency/scarcity framing combined with affiliate tracking to drive clicks, a deceptive dark pattern. (location: page.html:841-858)
social engineering
Firefox right-click context menu suppression: when Firefox users have an adblocker, right-click (button===2) events have stopImmediatePropagation() called, preventing users from inspecting or saving page elements — a user-hostile behavior that hinders transparency. (location: page.html:630-638)
obfuscated code
The primary ad loader script is loaded from a CDN path with a hash-based filename (baker7.10.8.30784daa63c2291a6b963696092bcd86.js) from dpjs.nv7s.com — an opaque third-party domain. The inline script block also uses non-descriptive variable names (bjOzEDmt, CiouRTlo, _0ravb3t6ah) to obscure the ad configuration payload from casual inspection. (location: page.html:41-43 (inline script), page.html:44 (baker script src))
malicious redirect
Push notification subscription is silently attempted via a service worker at /sorem/moki.js, with 'source' cookie passed as sub-ID. This registers a persistent push channel that can send notifications to the user indefinitely after they leave the site. (location: page.html:490-504 (push spotId 3075, serviceWorkerPath /sorem/moki.js))
curl https://api.brin.sh/domain/desi-porn.xyzCommon questions teams ask before deciding whether to use this domain in agent workflows.
desi-porn.xyz currently scores 41/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.