context safety score
A score of 44/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
domain spoof risk
domain has spoofing indicators (punycode/confusable/highly synthetic naming)
brand impersonation
The site operates on the IDN/punycode domain xn--3-lve1d0cya6hb2e.com, which decodes to the Tamil Unicode domain இசைமினி.com — a homograph/IDN squatting impersonation of the well-known piracy site isaimini.com. The page branding, title, and content all claim to be 'isaimini.com' and 'இசைமினி.com' while the actual serving domain is an encoded lookalike, deceiving users and automated agents into believing they are on the legitimate site. (location: domain: xn--3-lve1d0cya6hb2e.com; page title and all branding throughout page.html)
malicious redirect
All 14 download links on the page use a Google redirect wrapper (https://www.google.com/url?q=...) to launder traffic through Google's URL shortener/redirector to a third-party domain moviesda17.com. This technique disguises the true destination, abuses Google's trusted domain to bypass blocklists, and funnels users to an unrelated third-party piracy site. The ref= parameter varies (1 or 2), suggesting click tracking. (location: page.html lines 63-76, all <div class="dir"> anchor hrefs)
social engineering
The page encourages users to 'Like our Facebook Fan Page & Get Updates and News!' with an empty href anchor, a common tactic to build a social media following under a fake/piracy brand identity for future social engineering or phishing campaigns. The empty href prevents direct inspection of the target. (location: page.html line 19, <div class="bottom"> Facebook Fan Page link with empty href)
brand impersonation
The page extensively impersonates the legitimate brand 'isaimini.com' in its title, meta tags, h1/h2/h3 headings, and body text while operating from a different domain. Meta keywords and descriptions are keyword-stuffed to hijack search engine traffic from the real isaimini brand, constituting SEO-based brand impersonation to misdirect users seeking the legitimate site. (location: page.html lines 7-9, meta title/description/keywords; lines 25-46 body content)
curl https://api.brin.sh/domain/xn--3-lve1d0cya6hb2e.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
xn--3-lve1d0cya6hb2e.com currently scores 44/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.