context safety score
A score of 68/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
4 deceptive links where visible host does not match destination host
social engineering
Site presents itself as an authoritative 'best casinos' review portal targeting Kenyan users, using superlatives ('100% trustworthy', 'legit best online casinos', 'carefully test and vet') to build false credibility and drive users to gambling affiliate links via /go/ redirect URLs. All 'Play now!' CTA buttons route through internal redirect paths (e.g. /go/22bet-ke/, /go/paripesa-ke/) rather than directly to the casino, consistent with affiliate tracking and monetization. Users are socially engineered into trusting the site's recommendations without independent verification. (location: page.html:302-310, page.html:324-326 (casino table CTA buttons))
hidden content
A LiveInternet tracking pixel is hidden via CSS ('display:none' on #licnt7986) and loaded with a 1x1 transparent GIF base64 placeholder, then dynamically replaced with a remote tracking URL (https://counter.yadro.ru/hit) that exfiltrates user referrer, screen dimensions, page URL, and page title to a third-party Russian analytics service (yadro.ru) without any disclosed consent notice visible on the page. (location: page.html:1332-1346)
hidden content
The table of contents div (#ez-toc-container) is explicitly hidden via inline CSS ('display: none') but remains in the DOM with full navigational content, contributing to the 0.02 hidden content ratio flagged in the pre-scan. This is a minor SEO/content discrepancy rather than a malicious injection. (location: page.html:68-76)
malicious redirect
All casino affiliate 'Play now!' links route through internal redirect paths (/go/22bet-ke/, /go/paripesa-ke/, /go/helabet-ke/, /go/betwinner-ke/) rather than linking directly to external casinos. These opaque redirector paths can be repurposed to forward users to arbitrary destinations without the user being aware of the final destination before clicking. The 4 deceptive link hits flagged in the pre-scan align with these 4 redirect-wrapped CTA buttons. (location: page.html:325 (casino table rows with /go/ hrefs))
hidden content
12 base64 blobs flagged in pre-scan are accounted for: one is a CSS background SVG gradient image (inline data URI in .qa-q style, page.html:973), and one is the LiveInternet 1x1 GIF placeholder (page.html:1336). These are consistent with legitimate UI usage and not malicious payloads. No decoded injection or exfiltration content was found. (location: page.html:973, page.html:1336)
curl https://api.brin.sh/domain/bestcasinosonline.or.keCommon questions teams ask before deciding whether to use this domain in agent workflows.
bestcasinosonline.or.ke currently scores 68/100 with a caution verdict and medium 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.