context safety score
A score of 41/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
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 or upon fingerprint collection, indicating a traffic distribution system (TDS) used to route victims to downstream payloads based on profiling. (location: page.html:6-26, script block)
hidden content
A hidden anchor link ('Click here to enter') is wrapped in a div with 'display: none', pointing to the same tracking redirect URL with fp=-3. This hidden link is invisible to users but readable by crawlers and AI agents, potentially used to manipulate automated systems or as a fallback redirect mechanism. (location: page.html:32)
hidden content
A <noscript> meta-refresh redirect is present that immediately forwards non-JavaScript clients (including many bots and AI agents) to the tracking URL with fp=-5, ensuring no visitor escapes the redirect funnel regardless of browser capabilities. (location: page.html:33)
social engineering
FingerprintJS is loaded and executed silently to collect a unique visitor ID before redirecting. This fingerprinting is used to profile and track users without consent or disclosure, enabling targeted delivery of different payloads to different victim profiles (e.g., bypassing security scanners while serving malicious content to real users). (location: page.html:4, page.html:18-23)
malicious redirect
The domain jh83w9.cfd uses a random-looking subdirectory-free .cfd TLD (a TLD commonly associated with phishing and malware distribution infrastructure) and employs a UUID-based tracking redirect system (tr_uuid=20260306-1712-4281-b572-442fb1a918ad) consistent with a traffic distribution system that routes victims to phishing pages, malware, or credential harvesting sites based on their fingerprint profile. (location: page.html:6, metadata.json:domain)
curl https://api.brin.sh/domain/jh83w9.cfdCommon questions teams ask before deciding whether to use this domain in agent workflows.
jh83w9.cfd currently scores 41/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.