context safety score
A score of 35/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
Domain 28filmywap.com impersonates the well-known 'Filmywap' brand. The page title, meta tags, og:site_name, favicon, and footer all claim to be 'Filmywap (Official)' while operating from a numerically-prefixed lookalike domain. The canonical tag points to yet another variant (35filmywap.com), indicating a network of impersonation domains. (location: page.html:8-15, page.html:137)
malicious redirect
The canonical URL (rel=canonical) redirects users and search engines from 28filmywap.com to www.35filmywap.com. All content links, search form action, and navigation links also point to 35filmywap.com rather than the scanned domain. The 'Back To Home' link points to www.30filmywap.com — a third domain. This creates a multi-domain redirect network typical of piracy/malware distribution rings. (location: page.html:8, page.html:107, page.html:114, page.html:133)
social engineering
The site distributes copyrighted Bollywood, Hollywood, and OTT (Netflix) content for free download, luring users with promises of free HD movies (1080p/720p/480p). This is a known social engineering vector used to drive user engagement and expose visitors to malicious ads, unwanted installs, or credential harvesting on downstream pages. The listing of a Netflix-branded title ('Accused (2026) Netflix Bollywood Movie Download') falsely implies legitimacy. (location: page.html:84, page.html:94, page-text.txt:13-23)
brand impersonation
The site references and links to numerous other known piracy brand names (mp4moviez, 9kmovies, 9xmovies, filmyzilla, movierulz, etc.) as internal anchor links, likely to capture search traffic and impersonate or piggyback on those brands' reputations. (location: page.html:125, page-text.txt:54)
social engineering
A Telegram channel (t.me/filmywapbollywood) is prominently linked with a 'join us' banner image, used to funnel users into an unmoderated messaging channel — a common technique for distributing malware, scam links, and further phishing material outside the web context. (location: page.html:81)
hidden content
The page uses a WAP/mobile XHTML doctype (XHTML Mobile 1.0) which is unusual for a modern site and may be used to reduce rendering fidelity in security scanners. The .brin-context.md references a page-hidden.txt file for extracted hidden content that was not provided for analysis, suggesting additional hidden content may exist beyond what is visible in page.html. (location: page.html:1, .brin-context.md:16)
curl https://api.brin.sh/domain/28filmywap.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
28filmywap.com currently scores 35/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.