context safety score
A score of 43/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
cloaking
Page checks user-agent for bot/crawler strings to serve different content
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The site mydesi.sbs presents itself as 'Mydesi.net' throughout — in the page title, og:site_name, og:title, schema.org Organization name, logo alt text, and footer hero text ('The best porn videos are on Mydesi.net!'). The actual domain is mydesi.sbs, which is impersonating the established mydesi.net brand to divert traffic and trust. (location: page.html lines 24, 30, 33, 316, 1906-1908; metadata.json domain field)
malicious redirect
A third-party ad script is loaded from the suspicious domain 32451.gomatinequisheoi.com (commented as 'CA Pop'), which is a known pattern for pop-under/redirect ad networks that silently redirect users or open unsolicited tabs to malicious or scam destinations. The domain name is obfuscated and non-descriptive, characteristic of malvertising infrastructure. (location: page.html line 5: <script src="https://32451.gomatinequisheoi.com/4/js/238056" async></script>)
social engineering
Multiple video titles explicitly claim content is 'leaked', 'viral', or 'scandal' material (e.g., 'Indian Desi Hindi Sex MMS Videos Leaked', 'Young Indian Teen Girlfriend Sex Scandal Leaked', 'Horny Pakistani Couple Sex MMS Leaked Video'). This is a well-known social engineering pattern used to lure users into clicking, often leading to malvertising, credential harvesting pages, or malware downloads when content is gated. (location: page.html lines 586-596, 1714-1724, 1186-1196 and numerous other video blocks)
social engineering
Video titles referencing real named Indian social media influencers ('Indian Influencer Kamal Kaur Viral Sex MMS', 'Indian influencer Payal Gaming Viral MMS Leak Video') are used as lures. Attributing explicit content to real public figures is a social engineering technique to drive clicks and engagement, and is often used as a gateway to malvertising or scam pages. (location: page.html lines 610-624, 682-696)
curl https://api.brin.sh/domain/mydesi.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
mydesi.sbs currently scores 43/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.