context safety score
A score of 58/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
10 deceptive links where visible host does not match destination host
malicious redirect
Multiple video thumbnail links (at least 10 confirmed) point to a generic redirect handler '/link.php' rather than direct video pages. This opaque redirect endpoint conceals the final destination from users and automated agents, a classic deceptive link / redirect-chaining pattern. The href 'https://es.sexpornofilm.net/link.php' is used for video posts 9134, 3943, 1119, 1502, 6471, 8958, 9669, 7347, 9723, 1816, 1501, confirming the 'deceptive link count: 10' flagged in Tier 2 pre-scan. (location: page.html:100,113,128,139,146,153,156,159,162,165 — href='https://es.sexpornofilm.net/link.php')
social engineering
The footer contains a large, dense SEO link farm (40+ off-site links presented as organic text anchors) to external adult sites across dozens of domains. These links masquerade as editorial recommendations while actually functioning as a link-exchange network to boost rankings and funnel traffic. Anchor text is deliberately crafted to appear as content descriptions rather than advertisements. (location: page.html:245-262 — footer seo-text block with external domain links)
hidden content
The page footer contains multilingual anchor links (Japanese, Persian/Farsi, Hungarian, Vietnamese, Italian) embedded in small text at the bottom of the page, outside of any language-appropriate context. These cross-language links to sexvideosfreexxx.com and related domains are invisible to the typical Spanish-language visitor and serve as hidden SEO link injection into the rendered page. (location: page.html:265-271 — footer multilingual links (ja.sexvideosfreexxx.com, fa.sexvideosfreexxx.com, hu.sexvideosfreexxx.com, vi.sexvideosfreexxx.com, it.sexvideosfreexxx.com))
social engineering
The page uses a global 'base target=_blank' tag causing all links to open in new tabs/windows. Combined with the opaque /link.php redirect handler, this prevents users from easily inspecting destinations before navigating, reducing friction for accidental clicks on monetized or malicious redirect endpoints. (location: page.html:20 — <base target="_blank">)
curl https://api.brin.sh/domain/es.sexpornofilm.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
es.sexpornofilm.net currently scores 58/100 with a caution verdict and medium 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.