context safety score
A score of 43/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
cloaking
Page conditionally redirects based on referrer or user-agent
obfuscated code
A heavily obfuscated JavaScript block is injected at the very start of the <body> (before any visible content). It uses a Caesar-cipher-like character rotation via String.fromCharCode and charCodeAt to decode a packed string at runtime, then reconstructs URLs, domain names, and query-parameter lists from the decoded payload. The decoded strings and the subsequent network calls (URL parsing, random query-parameter injection, localStorage access) are never visible in plain source, making static analysis of the script's true targets impossible without dynamic execution. (location: page.html:7411 / page-text.txt:3)
malicious redirect
An external script is loaded from the suspicious domain 'badlandlispyippee.com' (//badlandlispyippee.com/on.js) with data-cfasync="false" to bypass Cloudflare rocket-loader. The domain name is randomly-looking gibberish typical of malvertising/traffic-distribution networks. The script's onerror/onload callbacks both invoke the obfuscated function 'jlxtutgs(15)', tying the suspicious obfuscated code directly to this third-party loader. This pattern is characteristic of malvertising redirectors that can send visitors to exploit kits, scam pages, or credential-harvesting sites. (location: page.html:7412)
hidden content
An inline CSS block written in Russian (Cyrillic comments) defines ad-cell grid classes (.jkawjkjgkjg, .ft-row, .ad-cell, .ad-scale) for iframes/images sized at exactly 300x250px — a standard ad unit — embedded via CSS transform-origin scaling. These classes and their associated markup appear in the extracted page-text.txt (lines 953–1018) but the actual ad iframe src attributes are blank in the scraped version, suggesting the ad slots are populated dynamically by the obfuscated script or the badlandlispyippee.com loader at runtime, hiding their true destination from static analysis. (location: page-text.txt:953-1018 / page.html (ad-cell section))
malicious redirect
The page body text contains an embedded promotional link to 'findfree.xxx' (anchor text 'free xxx') within editorial paragraph content, seamlessly blending a third-party outbound traffic redirect into what reads as the site's own descriptive text. Similarly, 'okporn.xxx' is linked in footer text. These cross-site affiliate redirect links inside body copy can send users (and AI agents following hyperlinks) to unvetted third-party destinations without clear disclosure. (location: page.html:7527, page.html:8349)
hidden content
A LiveInternet tracking pixel (counter.yadro.ru) is embedded and exfiltrates the full page URL, page title, referrer, and screen resolution of every visitor to a Russian analytics service (yadro.ru / liveinternet.ru). The pixel image is loaded via a JavaScript src assignment to bypass NoScript-style blocking and is disguised as a 1x1 transparent GIF. This constitutes undisclosed third-party data collection that harvests visitor navigation data. (location: page.html:8522-8531 / page-text.txt:1114-1119)
obfuscated code
Multiple large base64-encoded WOFF2 font blobs (data:font/woff2;base64,...) are inlined in the CSS. While font embedding is common, the sheer volume of inline base64 data (hundreds of kilobytes split across six @font-face blocks) can serve as a steganographic carrier or be used to inflate page weight to obscure other embedded payloads. Combined with the obfuscated JS, this warrants scrutiny. (location: page.html:15-68 (CSS @font-face blocks))
curl https://api.brin.sh/domain/allsex.xxxCommon questions teams ask before deciding whether to use this domain in agent workflows.
allsex.xxx currently scores 43/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.