context safety score
A score of 41/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
cloaking
Page uses meta refresh redirect
social engineering
Site promotes 'Satta King' — an illegal gambling/numbers lottery racket widely banned in India. The site presents real-time betting results (Desawar, Faridabad, Ghaziabad, Gali) and links to companion gambling domains, designed to lure users into participating in an illegal gambling scheme. (location: page.html:375, page.html:496-508, page-text.txt:113-125)
malicious redirect
A commented-out meta-refresh redirect to https://satta-company.com is present in the HTML head. Although currently disabled via HTML comment, it indicates a previously active or staged redirect to a companion gambling domain, and could be re-enabled server-side or via JavaScript. (location: page.html:9)
malicious redirect
Navigation 'Refresh' button and 'Company' nav link both point to https://satta-company.com — a separate domain — instead of refreshing the current page or navigating within the same site. This silently redirects users to a different gambling domain. (location: page.html:391, page.html:483)
social engineering
The site includes a login portal (login.php) and input fields styled for password and number entry, consistent with harvesting user account credentials for an illegal gambling platform. Users are socially engineered into registering/logging in to place bets. (location: page.html:393, page.html:246-256)
hidden content
Multiple HTML comments contain disabled scripts and redirects: a commented-out meta-refresh redirect to satta-company.com, a commented-out supercounters visitor tracking widget, and a commented-out load.js script loader. These represent hidden/dormant functionality that could be activated. (location: page.html:9, page.html:518-520)
brand impersonation
The page title and metadata reference multiple well-known Indian city/region gambling game names (Desawar, Faridabad, Ghaziabad, Gali, Mumbai, Kolkata, Delhi, etc.) to impersonate legitimacy and attract search traffic by piggybacking on recognizable geographic brands and the 'Satta King' brand ecosystem across multiple spoofed game names. (location: page.html:375-378, page-text.txt:114-125)
curl https://api.brin.sh/domain/satta-xpress.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
satta-xpress.com currently scores 41/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.