context safety score
A score of 32/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
encoded payload
suspicious base64-like blobs detected in page content
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The domain netflix.net serves a pixel-perfect replica of the official Netflix landing page (netflix.com), including Netflix branding, logo, color scheme, UI components, title 'Netflix - Watch TV Shows Online, Watch Movies Online', and all content sections (Trending Now, Enjoy on your TV, etc.). Origin-trial meta tags contain tokens cryptographically bound to netflix.com:443, indicating content was copied directly from the legitimate site. (location: page.html:1, metadata.json (domain: netflix.net))
phishing
The page displays a 'Sign In' button and a 'Get Started' email capture form on the lookalike domain netflix.net. Users who visit this domain believing it to be netflix.com will be prompted to enter their email address and credentials on a non-official domain, constituting a credential phishing attack. (location: page-text.txt line 17 ('Sign In'), page-text.txt line 33 ('Get Started'))
credential harvesting
An email input field and 'Get Started' CTA are rendered on the netflix.net impersonation page. The reactContext exposes API_ROOT pointing to https://www.netflix.com/api, suggesting submitted credentials or emails may be proxied to or compared against the real Netflix backend, enabling real-time credential validation and harvesting. (location: page-text.txt line 67 (reactContext API_ROOT), page-text.txt line 33 (Get Started CTA))
malicious redirect
The embedded reactContext sets 'host': 'www.netflix.com' and 'API_ROOT': 'https://www.netflix.com/api', indicating the site operates as a reverse proxy or transparent redirect layer. Requests and possibly session tokens initiated on netflix.net are routed through to netflix.com infrastructure, allowing session hijacking or man-in-the-browser attacks. (location: page-text.txt line 67 (serverDefs host and API_ROOT fields), page.html line 30610)
curl https://api.brin.sh/domain/netflix.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
netflix.net 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.