context safety score
A score of 29/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
script/meta redirect patterns detected in page source
cloaking
Page conditionally redirects based on referrer or user-agent
malicious redirect
Back-button hijacking script pushes 10 history states and intercepts popstate to redirect users to 'https://backbutton.videobaba.xyz/back-button-script/public/getit.php?site=XMI' when they try to navigate back. This traps users and forces them to an external redirect service. (location: page.html:1662-1758 (footer <script>); also page-text.txt:1618-1712)
malicious redirect
Navigation links in the header menu include external affiliate redirect links to 'https://kamareels2.com/?ref=MF-XMI&utm_medium=top_menu&utm_source=XMI' and 'https://fsiblog5.com/' opened in new tabs with rel='nofollow'. These redirect users to third-party adult sites via affiliate tracking parameters. (location: page.html:95-96)
hidden content
Client hint delegation meta tag delegates detailed browser fingerprinting data (sec-ch-ua, sec-ch-ua-bitness, sec-ch-ua-arch, sec-ch-ua-model, sec-ch-ua-platform, sec-ch-ua-platform-version, sec-ch-ua-full-version, sec-ch-ua-full-version-list, sec-ch-ua-mobile) to the third-party domain 'tsyndicate.com', enabling covert device fingerprinting of all visitors without their knowledge. (location: page.html:5)
hidden content
Third-party analytics script loaded from 'https://stats.indianpornempire.com/js/script.js' using a deferred Plausible-style tracker, silently collecting visitor traffic data for a cross-site network (indianpornempire.com) without disclosure on the page. (location: page.html:37)
hidden content
Ad injection scripts dynamically loaded from '//www.namastedharma.com/YbuIJY7.js' and '//www.namastedharma.com/PwlNLk2.js' and 'https://js.wpadmngr.com/static/adManager.js' at runtime based on referrer parameter. These third-party ad networks are injected conditionally and are not disclosed to users, enabling potentially malicious ad payloads. (location: page.html:1662-1758; page-text.txt:1618-1712)
hidden content
Revive ad server script loaded from '//blazingserver.net/revive/www/delivery/asyncjs.php' inserted inline within video thumbnail grid items. This third-party ad server (blazingserver.net) loads asynchronously and could serve arbitrary ad content including malvertising. (location: page.html:605, 1123)
social engineering
The site displays fake engagement statistics for injected ad units (e.g., '94K views', '94%' likes, '2 months ago') disguising ads as organic popular content to manipulate user click behavior on the 'Sexy reels XXX - KamaReels.com' ad placements embedded in video grids. (location: page.html:600-638, 1119-1155)
social engineering
The applyRefToLinks function dynamically rewrites all outbound hrefs to append a 'tubetraffic2' referral parameter when a visitor arrives via 'tubetraffic' referral, covertly modifying all links on the page to propagate affiliate tracking across clicks without user knowledge. (location: page.html:1677-1695; page-text.txt:1632-1650)
curl https://api.brin.sh/domain/xmishti.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
xmishti.com currently scores 29/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.