context safety score
A score of 49/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
brand impersonation
The site mr-jatt.im impersonates the well-known mr-jatt.com music platform, using nearly identical branding, title ('Mr-Jatt.Com Latest Punjabi Songs'), and keywords. The .im domain is used to clone the identity of the legitimate .com site, misleading users into believing they are on the original platform. (location: page.html:9-11, metadata.json:domain)
hidden content
A block of keyword-stuffed text is hidden from users via the HTML 'hidden' attribute. It contains dozens of competitor domain names and SEO spam terms (mr-jatt.com, mr-jatt.in, pagalworld, djjohal.com, etc.) invisible to visitors but readable by crawlers and AI agents, designed to manipulate search rankings and agent context. (location: page.html:165-181)
obfuscated code
Multiple script tags use a non-standard, obfuscated MIME type '337ded52825f17516c5a28a5-text/javascript' instead of 'text/javascript'. This is a Cloudflare Rocket Loader technique but is also used to delay or obscure script execution from security scanners. Scripts affected include the date display script, Google CSE loader, and Statcounter tracker. (location: page.html:121, page.html:140, page.html:190, page.html:195, page.html:203)
malicious redirect
A hyperlink on line 158 contains a malformed/unclosed href attribute: href="https://djpunjab.im> — the closing quote is missing, causing the attribute to bleed into adjacent HTML. This can result in unintended link behavior or redirect manipulation depending on browser parsing, and may be an intentional obfuscation technique. (location: page.html:158)
social engineering
The site falsely claims all content is provided under Creative Commons CC BY-NC-SA licenses, implying legitimacy for music downloads that are likely copyrighted. This misrepresentation encourages users to download potentially infringing content under a false sense of legal safety. (location: page.html:161)
curl https://api.brin.sh/domain/mr-jatt.imCommon questions teams ask before deciding whether to use this domain in agent workflows.
mr-jatt.im currently scores 49/100 with a suspicious verdict and medium 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.