context safety score
A score of 32/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
The site explicitly brands itself as 'NetFlix Mirror' in OG/Twitter meta tags (og:title and twitter:title both read 'NetFlix Mirror - Watch Movies and Series') and uses Netflix's characteristic black background, red accent color scheme, and content library framing to impersonate Netflix and other premium OTT platforms (Amazon Prime Video, Disney+, Hotstar). (location: page.html:16-23, meta og:title and twitter:title)
brand impersonation
Meta keywords explicitly list 'netflix,PrimeVideo,Disney+,Hotstar' to exploit brand recognition of major streaming services and attract users searching for those legitimate platforms. (location: page.html:6, meta name=keywords)
malicious redirect
The primary 'Go to Home' call-to-action buttons redirect users via onclick to an external domain 'https://net22.cc/home?utm_source=home_page' — a different domain entirely from netmirror.gg. This off-domain redirect with UTM tracking parameters is a classic traffic monetization or malicious redirect pattern used to funnel users to potentially harmful or ad-heavy third-party sites. (location: page.html:497, page.html:582)
malicious redirect
The iOS 'Download IOS DODO APP' button redirects through a link-anonymizing proxy 'https://href.li/?https://apps.apple.com/...' — use of href.li to obscure the true destination URL is a common technique to bypass URL scanners and hide the actual redirect target from users and automated tools. (location: page.html:554)
social engineering
The site instructs Android users to disable a core Android security feature: 'Enable(ON) install unknown apps on Setting > Security and privacy > install unknown apps > Google Chrome.' This pressures users into sideloading an APK (/NetMirror.apk) from an unverified source by bypassing Android's built-in protections against unknown app installations. (location: page.html:538, page-text.txt:50)
social engineering
Prominent red-text message 'Sign-In is Required to Use in Computer' creates urgency/pressure to authenticate, potentially priming users for credential harvesting on the destination site (net22.cc) after the redirect. (location: page.html:498, page-text.txt:10)
hidden content
A zero-dimension tracking pixel (width=0, height=0) is embedded in a hidden span element with id='trackamung', loading from //whos.amung.us — this invisibly tracks visitor activity without any user notice or disclosure in the visible page content. (location: page.html:611)
hidden content
A dynamically injected third-party analytics script from s10.histats.com is loaded asynchronously via document.createElement, obfuscating the external script load from casual inspection of static HTML and bypassing some content security controls. (location: page.html:661-665)
curl https://api.brin.sh/domain/netmirror.ggCommon questions teams ask before deciding whether to use this domain in agent workflows.
netmirror.gg currently scores 32/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.