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
social engineering
Site prominently advertises a paid membership/tipping service ('BIGG BOSS SIR') with tiered pricing (Vip 1 Day: 2500/-, VIP 1 WEEK: 5100/-, Vip 15 DAYS: 7500/-, Vip 1 MONTH: 11000/-) and claims to provide guaranteed winning numbers for an illegal gambling game, exploiting users financially under false pretenses of insider knowledge. (location: page.html lines 838-847, page-text.txt lines 471-479)
social engineering
Fabricated 'passing record' section shows claimed successful predictions by 'BIGG BOSS SIR' for multiple markets (MILAN DAY 05 JODI PASS, RAJDHANI DAY 38 JODI PASS, KALYAN 13 JODI PASS, etc.) to build false credibility and lure users into paying for the membership service. (location: page.html lines 829-848, page-text.txt lines 463-479)
hidden content
A complete login form (username/password inputs, submit button, registration link) with action pointing to 'login.php' is fully implemented in HTML but wrapped in a comment block (<!--div ... /div-->), hiding a credential-harvesting form from normal view while keeping the server-side handler potentially active. (location: page.html lines 766-776)
credential harvesting
A commented-out but fully functional HTML login form with POST method targeting 'login.php' collects username and password fields. If the comment is removed or the endpoint is accessed directly, it could harvest user credentials for the gambling platform. (location: page.html lines 767-775)
malicious redirect
Multiple prominent call-to-action buttons and a fixed floating link direct users to download an APK file (app-apna-release.apk) from the site itself rather than an official app store, bypassing Android security controls. The APK could contain malware or adware. (location: page.html lines 258, 1006)
social engineering
The site uses deceptive disclaimers ('for educational purposes only', 'we do not support gambling') while simultaneously operating an active illegal gambling results and tipping service with paid membership tiers, creating a false legal shield to manipulate users into believing the service is legitimate. (location: page.html lines 1013-1018, page-text.txt lines 647-651)
brand impersonation
The domain 'sattamatkadpboss.co' combines and mimics multiple well-known Indian gambling brand names ('dpboss', 'satta matka') to attract traffic from users searching for the original dpboss.net and other established matka sites, while claiming to be 'India's Biggest & Most Trusted' without verification. (location: page.html lines 6, 244-245, metadata.json)
curl https://api.brin.sh/domain/sattamatkadpboss.coCommon questions teams ask before deciding whether to use this domain in agent workflows.
sattamatkadpboss.co 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.