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
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page conditionally redirects based on referrer or user-agent
malicious redirect
Page contains a JavaScript-driven automatic redirect executed via setTimeout after 1 second. The script reads parameters from a cookie (__js_p_), computes a hash, sets tracking cookies (__jhash_ and __jua_), then unconditionally redirects the browser to a constructed URI via window.location.href. The destination is dynamically built from the referrer and cookie-controlled parameters, meaning the redirect target is not visible in static analysis and can be changed server-side by altering the __js_p_ cookie. This is a classic cloaking/redirect gate pattern used to serve different destinations to bots vs. real users. (location: page.html:36-48 (setTimeout redirect block))
obfuscated code
The get_jhash() function performs a computationally expensive loop (1,677,696 iterations) to derive a hash value from a cookie-supplied seed. This is a bot-detection / proof-of-work challenge designed to fingerprint or gate visitors, a technique commonly used by traffic distribution systems (TDS) and malvertising chains to distinguish automated crawlers from real browsers before serving malicious payloads or redirects. (location: page.html:7 (get_jhash function))
hidden content
The page renders no visible content to users or crawlers. The entire body consists of a single centered GIF image (an ajaxload spinner encoded as a data URI) and a script block. The meta tag 'robots: noindex, noarchive' instructs search engines not to index or cache the page, a deliberate measure to prevent archival and analysis of the page's behavior — a strong indicator of a cloaked or intermediary redirect page. (location: page.html:1 (meta robots noindex,noarchive) and page.html:2 (body with spinner only))
obfuscated code
The page collects and exfiltrates the visitor's full User-Agent string by writing it into a cookie (__jua_) with a server-controlled max-age and SameSite/Secure flags derived from cookie parameters. This enables server-side fingerprinting and selective targeting of specific browser environments, consistent with exploit kit landing page behavior. (location: page.html:43 (document.cookie __jua_ assignment))
social engineering
The page presents only an animated loading spinner with no branding, navigation, or content, creating an artificial 'loading' impression to hold the user's attention for the 1-second delay before the JavaScript redirect fires. This is a social engineering pattern that prevents user suspicion during the redirect gate delay. (location: page.html:2 (data URI spinner GIF as sole visual content))
curl https://api.brin.sh/domain/trueconf.ruCommon questions teams ask before deciding whether to use this domain in agent workflows.
trueconf.ru 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.