context safety score
A score of 40/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
malicious redirect
script/meta redirect patterns detected in page source
social engineering
Site repeatedly promises '100% FIX' gambling tips with 'MONEYBACK GUARANTEE' and claims users can 'cover all losses in 1 day' by paying an advance fee of Rs. 3000-3100. This is a classic advance-fee fraud targeting gamblers with false certainty of wins. (location: page.html lines 206-210, 279-283, 580-585; page-text.txt lines 129-133, 162-166, 457-462)
credential harvesting
A login form on the homepage collects Email/Phone and Password credentials and submits them via POST to https://matka420.live/login. The site operates an illegal gambling service, making this credential collection high-risk. A CSRF token is embedded in the form. (location: page.html lines 484-512)
malicious redirect
A fixed floating 'PLAY MATKA' button uses onclick JavaScript to redirect users to https://ten11.fun/vip777.apk — a third-party domain serving an Android APK file. Silently redirecting users to download an APK from an unrelated domain is a known malware/spyware distribution vector. (location: page.html lines 1395-1398)
hidden content
Multiple commented-out blocks contain previously active redirect buttons and links to third-party gambling platforms: https://cutt.ly/StarGames (URL shortener redirect), https://sara567.shop/, and https://chat.whatsapp.com/ISA6W05heV9HyKYNwh4h3S. These are concealed from users but preserved in source, indicating prior affiliate/redirect schemes. (location: page.html lines 188-258, 1325-1380)
hidden content
Google Analytics script tags use a non-standard type attribute value '39ca0fa2b321326785c63706-text/javascript' instead of 'text/javascript'. This is a Cloudflare Rocket Loader obfuscation token, but it also masks which scripts execute on page load and could be used to hide script execution from basic scanners. (location: page.html lines 54-61)
social engineering
The site targets financially vulnerable users by framing illegal gambling as a legitimate income source and financial solution ('become free from financial problems', 'alternative source of income'), actively encouraging users in financial distress to bet money on a rigged-odds game. (location: page.html lines 1183-1185, 1210; page-text.txt lines 1057-1059, 1084)
malicious redirect
An active aside block links to https://ten11.fun/vip777.apk via an image banner labeled 'Vip 777', presenting a third-party APK download as a legitimate in-page advertisement without disclosure that it is an external executable download. (location: page.html lines 259-271)
curl https://api.brin.sh/domain/matka420.liveCommon questions teams ask before deciding whether to use this domain in agent workflows.
matka420.live currently scores 40/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.