context safety score
A score of 33/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
obfuscated code
Heavily obfuscated JavaScript block using multi-layer encoding: URI-encoded string decoded via decodeURI(), then character substitution cipher (Caesar-style with position-dependent shift mod 95), split into indexed substrings, and reassembled into executable code. The obfuscation pattern is consistent with ad-fraud or drive-by malware loaders used to hide payload URLs and execution logic from static scanners. (location: page.html:line 99 — <script data-cfasync="false">!function(){"use strict";for(var n=decodeURI("wd%60andp%5E..."))
malicious redirect
Third-party ad script loaded from cupbearergrowllurch.com, an unrecognized domain with a nonsensical name pattern characteristic of malvertising infrastructure. Loaded with data-cfasync="false" to bypass Cloudflare inspection, paired with onerror/onload callbacks (btabbuqd) defined inside the obfuscated block above — strongly suggesting a coordinated ad-injection or redirect chain. (location: page.html:line 100 — <script data-cfasync="false" data-clocid="2090594" async src="//cupbearergrowllurch.com/on.js")
malicious redirect
Third-party script loaded from lf.enrolcopals.com — another unrecognized domain with characteristics of ad-network or malvertising infrastructure. Injected inline within the notification/chat content area of the page rather than in a standard script section, suggesting it was added covertly. (location: page.html:line 179 — <script data-cfasync="false" async type="text/javascript" src="//lf.enrolcopals.com/sg3Dl3b7ENrLJ/137104">)
malicious redirect
Third-party ad script loaded from acscdn.com via aclib.runBanner() with zone ID 11004342. acscdn.com is associated with AdCash, an ad network historically linked to malvertising campaigns that redirect users to scam and phishing pages. Placed inside the visible notification area to ensure execution. (location: page.html:line 170-178 — aclib.runBanner({ zoneId: '11004342' }) via //acscdn.com/script/aclib.js)
social engineering
The site's notification box instructs users that if the current domain (dualeotruyenpe.com, age 42 days) is inaccessible, they should visit dualeotruyenKY.COM instead, and recommends using the 1.1.1.1 app for faster access. This is a classic domain-cycling technique used by piracy/grey sites to maintain audience across domain seizures or blocks, normalizing user redirection to unvetted domains. (location: page.html:line 168-169 — 'Nếu không truy cập được website, hãy truy cập vào: dualeotruyenKY.COM. Hoặc dùng app 1.1.1.1')
hidden content
Multiple og:image and Twitter card image meta tags contain the literal unresolved template placeholder '{minh_hoa}' rather than an actual URL. This indicates the page was generated from a template with unfilled variables, which may be used to obscure the true origin or nature of content from crawlers and security scanners. (location: page.html:lines 21, 24, 25, 31 — content="{minh_hoa}")
malicious redirect
The canonical URL and og:url both point to https://dualeotruyenky.com/ rather than the actual scanned domain dualeotruyenpe.com (42 days old). The footer and tag container also link exclusively to dualeotruyenky.com. This mismatch between the serving domain and the canonical/og domain suggests dualeotruyenpe.com is a shadow/mirror domain funneling traffic and SEO authority to the primary domain, a technique commonly used to evade domain-level blocks. (location: page.html:lines 18, 36 — og:url and canonical both set to https://dualeotruyenky.com/)
curl https://api.brin.sh/domain/dualeotruyenpe.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
dualeotruyenpe.com currently scores 33/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.