context safety score
A score of 35/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
malicious redirect
Multiple third-party affiliate/ad links use obfuscated tracking subdomains and redirect chains to external sites: 'aplsof2fd.nubrenplovrybhsrvikvornux.com', 'aplsof2fd.flirnapolfwemvrybhszorex.com', 'ba8.ydcfrfo.xyz', 'ef991.enwlvmt.xyz', 'dy.vlyzaglundortravreotxlkan.com'. These domains use randomized substrings consistent with cloaked redirect infrastructure used to evade blocklists. (location: page.html:313-318 (index_ddg ad block))
social engineering
Site hosts and prominently promotes a large catalog of adult fiction content including explicit non-consent, incest, hypnosis/drugging, and minor-targeting categories (萝莉/loli, 正太/shota). Content is designed to normalize coercive sexual scenarios, which can be used for grooming and desensitization. Categories explicitly labeled include 强奸 (rape), 凌辱 (humiliation/abuse), 萝莉 (loli), 正太 (shota). (location: page.html:97-129 (category nav), page.html:276-304 (featured listings))
hidden content
Yandex Metrika tracking pixel is loaded with position:absolute; left:-9999px — a classic off-screen hidden tracker. This silently exfiltrates user behavioral data (clickmaps, link tracking, bounce tracking) to Yandex servers (mc.yandex.ru) without visible disclosure to users. (location: page.html:1303 (noscript img tag), page-text.txt:1283)
hidden content
Histats tracking pixel (sstatic1.histats.com/0.gif) is loaded inside a noscript tag as a fallback tracker, invisibly collecting visitor data. Combined with Yandex Metrika and Microsoft Clarity (qmusj6utmx), this site runs three concurrent covert analytics/tracking systems on users. (location: page.html:1328 (noscript Histats pixel))
malicious redirect
An iframe-based age gate is dynamically injected via JavaScript, loading '/jump/age_gate.html' at z-index:10000 over the full page. It communicates via postMessage ('ageVerified') to remove itself. This pattern can be used as a clickjacking or social-engineering layer — the iframe source is controlled by the same origin and could be swapped to capture interaction or redirect users. (location: page.html:1253-1277)
social engineering
External link to 'xn--i8s951di30azba.com' (punycode-encoded domain, decodes to a Chinese adult/AI companion site) uses a referral parameter (?rf=0f9dde1a), indicating a monetized affiliate funnel routing users to a third-party 'AI girlfriend' service. Punycode domain obscures the actual destination from casual inspection. (location: page.html:313 (AI女友 link))
prompt injection
The site's meta keywords and description fields (page.html:6-7) contain explicit adult content taxonomy in Chinese. If an AI agent scrapes or indexes this page, these fields could cause unexpected behavioral shifts in content classifiers or safety filters — functioning as a soft prompt injection through metadata poisoning of the AI's context window with sexually explicit categorical terms. (location: page.html:6-7 (meta keywords and description tags))
curl https://api.brin.sh/domain/alicesw.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
alicesw.com currently scores 35/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.