context safety score
A score of 37/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
encoded payload
suspicious base64-like blobs detected in page content
social engineering
Real-money gambling platform targeting Indian users with promises of 'instant withdrawals', 'free cash', 'free spins', 'bonus codes', jackpots, and promo codes distributed via WhatsApp and Telegram. These tactics are classic social engineering patterns designed to lure users into depositing real money through urgency and reward framing. (location: page.html:23 (meta description), page-text.txt:1)
social engineering
Game listings display fabricated future timestamps (e.g., '2025/08/21', '2025/08/09', '2025/07/26') presented as upcoming releases to create artificial urgency and FOMO (fear of missing out), manipulating users into signing up or depositing early. (location: page-text.txt:1 (game listings with future dates))
hidden content
Page contains an unusually large volume of HTML comments (146 entries in page-hidden.txt) consisting entirely of bracket characters '[' and ']'. This pattern is consistent with Vue/Nuxt SSR comment delimiters used as rendering anchors, but the sheer volume could also indicate stripped or obfuscated content that was removed before scanning. The rendered page may differ from what was captured. (location: page-hidden.txt:1-146)
social engineering
Bonus distribution channels explicitly named as WhatsApp and Telegram — platforms commonly used to bypass regulated app stores, evade detection, and distribute unofficial APKs or phishing links to users who opt in through the site. (location: page.html:23 (meta description: 'bonus codes via WhatsApp and Telegram'))
phishing
The page title is heavily keyword-stuffed ('UONO PLAY |UONOPLAY |UONO PLAY GAMES | UONO PLAY DOWNLOAD | UONO PLAY TRICKS') which is a common SEO manipulation tactic used by fraudulent gambling and phishing sites to capture organic search traffic from users seeking legitimate gaming platforms. (location: page.html:3 (title tag))
curl https://api.brin.sh/domain/uonoplay.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
uonoplay.com currently scores 37/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.