context safety score
A score of 43/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 solicits phone contact (Call-09752892991) and advance payments (Advance=2500rs) for gambling tips, framing illegal betting predictions as 'free service' (SamajSeva). This is a classic advance-fee social engineering scheme targeting gamblers with false promises of 100% guaranteed winning numbers ('100% paas hokar milega'). (location: page.html:1151-1157, page-text.txt:848-857)
social engineering
Disclaimer falsely claims the site is a 'News Publishing Website' with no connection to gambling, while the entire site is dedicated to live illegal Satta Matka gambling results, tips, and betting predictions. This deceptive framing is designed to evade legal and platform enforcement while continuing to operate an illegal gambling service. (location: page.html:1511-1516, page-text.txt:1201-1204)
social engineering
Site repeatedly makes false authority claims ('most reliable and popular platform', 'trusted by thousands', '100% accurate') and promises of guaranteed winnings to lure users into engaging with an illegal gambling operation. Urgent calls-to-action ('Start Today!', 'BookMark Now!!', 'win your money today!') amplify manipulative pressure tactics. (location: page.html:325-344, page-text.txt:25-47)
social engineering
WhatsApp channel link embedded as a fixed floating button directs users to an external messaging channel (whatsapp.com/channel/0029VbBj10vCMY08EKieST0h), likely used to further solicit advance payments or harvest contact information outside the website context. (location: page.html:1332)
hidden content
HTML character entity encoding used for Hindi text in the page body (सबसे etc.) to obfuscate Devanagari script content from plain-text scrapers. While not malicious in isolation, it is a minor obfuscation technique used to partially hide promotional text from automated content analysis. (location: page.html:1124)
curl https://api.brin.sh/domain/sattamatkano1.meCommon questions teams ask before deciding whether to use this domain in agent workflows.
sattamatkano1.me currently scores 43/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.