context safety score
A score of 38/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
Site explicitly positions itself as a 'free alternative to Netflix', mimicking Netflix's brand value proposition and feature set to attract users under false pretenses of legitimacy. (location: page.html:118, page-text.txt:68)
obfuscated code
Two identical heavily obfuscated JavaScript blocks use a character-interleaving string encoding technique to hide their true behavior. The code dynamically constructs function names, manipulates the DOM, intercepts document methods (including querySelector), creates hidden iframes, and overrides localStorage — all hallmarks of malicious anti-analysis evasion. (location: page.html:41, page.html:220)
hidden content
A hidden iframe loads 'https://sysmeasuring.net' with style='display:none', silently making a cross-origin request to an external tracking/measurement domain without user knowledge or consent. (location: page.html:229)
hidden content
An H1 element is placed inside a div with 'display:none', hiding the site name from users while keeping it visible to crawlers and automated agents for SEO manipulation. (location: page.html:47-52)
social engineering
Site repeatedly claims to be 'ad-free', 'safe from viruses', and that users do not need VPN or antivirus — while simultaneously running obfuscated scripts and a hidden iframe. These false safety assurances are designed to lower users' security guard. (location: page.html:115, page.html:130, page-text.txt:80)
social engineering
Content disparages competing free streaming sites as 'ill-intentioned' and 'filled with malicious ads' to steer users toward SFlix, creating false trust through fear of alternatives. (location: page.html:122, page-text.txt:72)
malicious redirect
External link to 'https://9animetv.to/' uses rel='dofollow' and target='_blank', indicating a paid affiliate or link-exchange relationship with another piracy site, potentially exposing users to malicious content on that destination. (location: page.html:189)
obfuscated code
The obfuscated script intercepts and overrides document.createElement and document.querySelector, allowing it to silently inject or replace DOM elements. This pattern is used in credential harvesting overlays and ad injection attacks. (location: page.html:41, page.html:220)
curl https://api.brin.sh/domain/sflix.psCommon questions teams ask before deciding whether to use this domain in agent workflows.
sflix.ps currently scores 38/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.