context safety score
A score of 44/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page uses meta refresh redirect
malicious redirect
Page immediately redirects all visitors via JavaScript (window.location.replace) to a tracking URL with a UUID and browser fingerprint parameter. The redirect fires within 300ms via setTimeout as a fallback, ensuring no visitor escapes the redirect regardless of fingerprint availability. (location: page.html:6-26, script block)
hidden content
A hidden anchor link (<div style='display: none;'>) contains a pre-fingerprinted redirect URL (fp=-3). This link is invisible to human users but crawlable by bots and AI agents, serving as a covert redirect vector or cloaking mechanism. (location: page.html:32)
hidden content
A <noscript> meta-refresh redirect is embedded to silently redirect non-JavaScript clients (including some AI agents and scrapers) to a tracking URL with fp=-5, bypassing script-based detection avoidance. (location: page.html:33)
social engineering
The only visible text on the page is 'Click here to enter', a minimal social engineering prompt designed to entice user interaction while the real redirect happens automatically in the background via JavaScript. (location: page.html:32, page-text.txt:2)
hidden content
Browser fingerprinting is performed via FingerprintJS (iife.min.js) before redirecting the user. The fingerprint visitorId is appended to the redirect URL, enabling persistent cross-site tracking and user profiling without consent disclosure. (location: page.html:4, page.html:18-23)
curl https://api.brin.sh/domain/sktorrent.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
sktorrent.net currently scores 44/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.