context safety score
A score of 37/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 checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
malicious redirect
JavaScript implements a browser history manipulation trap: when a user arrives from an external referrer, it injects 15 history entries appending '#!/back', then intercepts the browser back-button to redirect the user to '/play.php?back' instead of returning to the previous site. This is a classic exit-trap technique that hijacks navigation and forces users onto a different page. (location: page.html:1793 and page.html:1828)
hidden content
Dynamic ad content is loaded from server-side PHP endpoints (/ad00.php, /ad000.php, /adv.php, /livewebcam.php, /toplist.php) via jQuery .load() after page render. This deferred injection hides content from static analysis and can deliver payloads (ads, popups, redirects) that are not visible in the initial HTML. (location: page.html:1769, 1772, 1801, 1804, 1807, 1836, 1839-1840)
prompt injection
Bot detection logic explicitly enumerates and excludes a large list of known web crawlers and AI agents (including 'AISearchBot', 'Applebot', 'bingbot', 'googlebot', and many others) from seeing ad content and the history-manipulation redirect trap. Non-bot users (including AI browsing agents that don't match the pattern) are subjected to the redirect trap and dynamic ad injection, while bots see a clean page — a classic cloaking technique targeting AI agents. (location: page.html:1756-1763 and page.html:1791-1798)
social engineering
A video listing title embeds an external URL directly in its visible title text: 'Sexy Webcam Couple Nude Sex Video -- Full Video Link Here - Https://khabarbabal.online/file/mzdjot'. This entices users (and potentially AI agents scraping titles) to visit an unvetted third-party domain (khabarbabal.online) via a shortened/opaque file path, a common technique for traffic hijacking or malware distribution. (location: page.html:838-843)
credential harvesting
A video listing title contains a personal Gmail address: 'I Am Independent Call Boy Service In Delhi Ncr ravipandat91@gmail.com'. The email is obfuscated using Cloudflare's email protection (data-cfemail encoding) in the rendered HTML, but the decoded address appears in page-text.txt. Embedding contact emails in content on adult sites is used for social engineering and contact harvesting. (location: page.html:1076-1087, page-text.txt:1046)
curl https://api.brin.sh/domain/ahindian.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
ahindian.com currently scores 37/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.