context safety score
A score of 29/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
1 deceptive links where visible host does not match destination host
social engineering
Site promotes illegal gambling (Satta Matka) with deceptive claims of '99.99% accurate' guesses, '100% Fix Game', 'Money Back Guarantee', and 'guaranteed win' language designed to manipulate users into financial risk. Content actively solicits users to bet money with false promises of certainty. (location: page.html:596-598, page.html:1558, page-text.txt:116-118)
social engineering
Dedicated 'Fix Game' page linked in footer (satta-matka-fix-game.php) and prominent 'VIP Guessing Program' upsell soliciting users to pay for 'fixed' gambling results — a classic fraud scheme targeting gamblers with promises of pre-determined outcomes. (location: page.html:1612, page.html:1518)
brand impersonation
Domain dpbosss.net.in (triple 's') impersonates the well-known dpboss.net brand. The site references dpboss.net and dpboss.com as authoritative sources while operating under a typosquatting domain. Keywords in metadata include 'dpbosss.com' as an alias, establishing deliberate brand confusion. (location: metadata.json:1, page.html:7-8, page.html:1570)
malicious redirect
Multiple prominent calls-to-action redirect users to saionline.fun, a third-party gambling application site entirely separate from the hosting domain. The redirects are embedded as primary CTAs ('Download Now', 'Play Download', 'Play Now') throughout the page, funneling users to an unvetted external domain. (location: page.html:462, page.html:466, page.html:571, page.html:588, page.html:1626)
social engineering
WhatsApp contact using a US phone number (+15022020710) is prominently promoted for 'VIP game' and 'Fix Game' access, with claims of '100% fix 1 open 1 jodi 2 patti' and money-back guarantee. This is a common advance-fee fraud vector where victims are lured into paying for 'insider' gambling tips. (location: page.html:600, page.html:1623, page-text.txt:120)
hidden content
Inline CSS injected mid-body (inside a div, after result sections) defines styling for the live results area. This `<style>` tag inside `<body>` (not `<head>`) alongside a stray `<meta http-equiv='Content-Type'>` tag injected mid-document suggests content injection or template manipulation that may obscure additional embedded content from scanners. (location: page.html:476, page.html:563)
hidden content
JavaScript blocks right-click (contextmenu), keyboard shortcuts Ctrl+S, Ctrl+U, Ctrl+Shift+I, and F12, actively preventing users and security tools from inspecting page source. This is an anti-analysis technique used to conceal malicious or deceptive content from casual inspection. (location: page.html:53-61)
social engineering
Disclaimer is designed to shift legal liability onto users rather than genuinely warn them, while the rest of the page actively promotes gambling participation. The disclaimer states gambling 'may be illegal in your region' while simultaneously encouraging play — a regulatory evasion technique. (location: page.html:1602-1605, page-text.txt:1123-1124)
curl https://api.brin.sh/domain/dpbosss.net.inCommon questions teams ask before deciding whether to use this domain in agent workflows.
dpbosss.net.in currently scores 29/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.