context safety score
A score of 47/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
On page load, an AJAX call is made to https://dian4d6.forum/get-configuration?ref_id= and if the server returns a non-null 'redirect' field, the page immediately executes window.location.href = data.redirect — an unconditional server-controlled redirect to an arbitrary URL with no validation or user consent. (location: page.html:1505-1507 and page.html:1501-1506)
social engineering
The site is an unlicensed Indonesian online gambling platform (togel/lottery, slots, live casino, sabung ayam/cockfighting) disguised with legitimate-sounding 'game online' marketing copy. It uses aggressive bonus language (Bonus Deposit 200%, Cashback 100%, New Member 100%) and urgency framing to solicit real financial deposits via QRIS, OVO, GoPay, Dana and major Indonesian banks. (location: page.html:565-641, page-text.txt:841-872)
credential harvesting
The site presents login (MASUK) and registration (DAFTAR) forms at /masuk and /daftar that collect usernames, passwords, and email addresses for an unregulated gambling platform. Multiple game provider tiles also redirect unauthenticated users directly to /masuk, funneling all visitors toward credential submission. (location: page.html:428-435, page.html:792-831)
malicious redirect
The canonical URL and og:url meta tags point to https://dian4dwin.com while the serving domain is dian4d6.forum, and an amphtml alternate link points to https://dian4d7.space/amp — indicating a multi-domain redirect/SEO cloaking network designed to shuttle users between related gambling domains. (location: page.html:16-18, page.html:23-24)
social engineering
The footer SEO copy deliberately frames an illegal gambling site as a legitimate 'game online provider' with claims of data security, 24/7 customer support, and multi-device compatibility — written to pass automated content moderation and mislead users about the nature of the platform. (location: page.html:1420-1451, page-text.txt:841-872)
hidden content
A welcome modal (class 'setting_welcome') is initialized as display:none and its body content is injected dynamically from the server API response (data.setting_welcome.description and data.setting_welcome.path_link) via unsanitized innerHTML append — allowing the server to inject arbitrary HTML/content into the page that is not present in the static source. (location: page.html:1068-1081, page.html:1509-1517)
prompt injection
The /get-configuration API response is used to dynamically build and inject HTML strings directly into the DOM via jQuery .append() with no sanitization (including data.domain, value.id, value.name, value.logo_link, value.prize_*_split, etc.). A compromised or malicious API response could inject script tags or event handlers into the page, posing a prompt injection / XSS escalation risk for any AI agent that fetches and processes this page's rendered output. (location: page.html:1529-1615)
social engineering
The APK download link (https://apk.layarponsel.com/dian4d/dian4d.apk) in the circular menu prompts users to sideload an Android application from a third-party non-app-store domain, bypassing platform security controls and potentially delivering malicious software. (location: page.html:1063-1066)
curl https://api.brin.sh/domain/dian4d6.forumCommon questions teams ask before deciding whether to use this domain in agent workflows.
dian4d6.forum currently scores 47/100 with a suspicious verdict and medium 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.