context safety score
A score of 33/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
social engineering
Site repeatedly promotes paid 'fix game' tips requiring upfront payment (1500-2500 Rs) before receiving gambling tips via SMS, exploiting users' desire for guaranteed wins. Classic advance-fee fraud pattern targeting gamblers. (location: page.html lines 1099-1106, 1157-1161, and repeated across all market result sections; page-text.txt lines 316-318, 997-1001)
malicious redirect
Download buttons labeled '📲 Fallow What's Up Channel 👍' actually link to an APK file at https://indian--matka.com/images1/indianmatka4.apk — the domain uses a double-dash homoglyph/typosquat on 'indian-matka.com' and serves a direct APK download, not a WhatsApp channel. The original WhatsApp link is commented out and replaced with this APK link. (location: page.html lines 1125-1126, 1180-1181, 1235-1236, 1290-1291, 1345-1346, 1400-1401, 1455-1456, 1510-1511, 1565-1566, 1620-1621, 1675-1676, 1730-1731)
hidden content
A download/app promotion box with deposit bonus offers (300-5000 Rs tiers) is set to 'display: none' — the element is hidden from view but present in the DOM. It promotes an APK download with deposit bonuses, invisible to casual visitors but potentially served to targeted users or bots. (location: page.html lines 1968-1992)
social engineering
False disclaimer claims the site is a 'News Publishing Website' with no connection to gambling, while the entire page is dedicated to promoting illegal gambling, collecting payments for 'fix' game tips, and encouraging users to deposit money. This deceptive disclaimer is designed to evade legal scrutiny and AI/automated content filters. (location: page.html lines 834-836; page-text.txt lines 52-54)
social engineering
Membership payment scheme advertised with tiered fees (1-week: 2500 Rs, VIP: 3500 Rs, 1-month: call) promising 'Fix Single Open', 'Fix Single Jodi & Penal' gambling tips after payment. Uses urgency and false legitimacy to extract upfront fees with no verifiable service. (location: page-text.txt lines 2841-2930)
brand impersonation
The site misrepresents itself using a canonical link to amp.dev documentation (https://amp.dev/documentation/guides-and-tutorials/start/create/basic_markup/) in the page head, creating a false association with Google's AMP project to appear legitimate and improve search ranking. (location: page.html line 12)
social engineering
Fabricated social proof claims ('5820+ happy customers across Pen India') are embedded in content text and used as anchor text in chart descriptions to manufacture false credibility for the gambling operation. (location: page-text.txt lines 3428-3432, 3500-3502)
hidden content
CSS uses .Milan_Night class to hide kalyan_ad_title, kalyan_ad_details, and download_box for most result sections while only displaying them for KALYAN section — allowing selective ad injection based on CSS class manipulation, potentially to show/hide content conditionally for different audiences or bots. (location: page.html lines 1065-1074)
curl https://api.brin.sh/domain/sattaindianmatka.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
sattaindianmatka.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.