context safety score
A score of 25/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
social engineering
Site displays fabricated winning testimonials with partially redacted user IDs (e.g., 'oxxxx11', 'ixxxxxxx57', 'bxxxx17') claiming winnings of Rp.152,800,000, Rp.91,180,000, and Rp.90,000,000 to lure users into depositing money on an online gambling platform. Classic fake social proof tactic. (location: page.html lines 466-578, page-text.txt lines 365-479)
social engineering
Site aggressively promotes low minimum deposit (Rp10,000) and guaranteed payouts ('setiap kemenangan berapapun pasti dibayarkan penuh') to psychologically pressure users into gambling, typical of fraudulent online gambling operations. (location: page.html lines 474-478, page-text.txt lines 375-379)
malicious redirect
Login and registration links in the navigation menu redirect users from lunablog925.com to an entirely different domain, luna34481.com, without disclosure. The blog domain appears to function solely as a traffic funnel to the actual gambling platform at luna34481.com. (location: page.html lines 147-148 (menu-item-37, menu-item-36))
malicious redirect
Multiple CTA buttons (LIHAT PROMO, DEPOSIT SEKARANG, HADIAH TERBESAR, BETTING SEKARANG) redirect to luna34481.com, a separate off-domain gambling site, without user disclosure that they are leaving the current domain. (location: page.html lines 317-402)
malicious redirect
Primary hero CTA button 'Kunjungi Kami' links to https://luna34481.com/register, directing users to register on a separate off-domain gambling site. (location: page.html line 236)
malicious redirect
APK download button links to https://gplaystore.id/pwa/08685927/, a third-party domain impersonating Google Play Store (gplaystore.id vs play.google.com) to distribute potentially malicious mobile app. (location: page.html line 260)
brand impersonation
Domain gplaystore.id is used to host and distribute a mobile app download, closely mimicking the legitimate Google Play Store domain (play.google.com). This could deceive users into installing unvetted APKs. (location: page.html line 260)
social engineering
Site uses a 'noindex, nofollow' robots meta tag to hide from search engine crawlers while still serving content to users, a tactic commonly used by fraudulent sites to avoid detection and de-indexing. (location: page.html line 10)
social engineering
Background image and CSS assets are loaded from lunablog997.com and lunablog22.net, separate domains in the same cluster, suggesting a coordinated network of related gambling affiliate/funnel sites sharing assets. (location: page.html lines 67 (lunablog22.net), 90 (lunablog997.com))
malicious redirect
'RTP GACOR' button links to rtpslotluna215.com, another off-domain site presenting 'Return to Player' slot data, part of the broader gambling funnel network. (location: page.html line 419)
curl https://api.brin.sh/domain/lunablog925.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
lunablog925.com currently scores 25/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.