context safety score
A score of 37/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
phishing
1 deceptive links where visible host does not match destination host
cloaking
Page checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The domain sarkariresult.com.cm uses a .cm TLD (Cameroon) to impersonate the well-known Indian government job portal SarkariResult.com. The site explicitly claims to be 'the official website of Sarkari Result' and presents itself as an authoritative source for Indian government exam results, jobs, and admit cards, while the disclaimer buried at the bottom admits it is not associated with any official or government websites. (location: page.html:18, page.html:682, page-text.txt:434)
social engineering
The site falsely and prominently claims 'SarkariResult.com.cm is the official website of Sarkari Result' targeting Indian job-seekers who search for government exam results. This deceptive authority claim is designed to build false trust among users seeking sensitive government information such as exam results, admit cards, and job applications. The disclaimer contradicting this claim is buried and not prominently displayed. (location: page.html:682, page-text.txt:434, page-text.txt:439)
brand impersonation
The site's title, meta tags, og:site_name, and schema.org markup all assert 'Sarkari Result' branding and present the .com.cm domain as the canonical/official source. The JSON-LD schema even labels the page type as 'NewsArticle' and 'SearchResultsPage' with the headline 'Sarkari Result, Sarkari Result 2025 | Sarkari Results | Sarkariresult' — mimicking the presentation of the legitimate sarkariresult.com site to deceive search engines and AI agents indexing or summarizing this content. (location: page.html:18, page.html:33)
social engineering
The site collects WhatsApp channel subscriptions (https://whatsapp.com/channel/0029VaAbQf01NCrYADMLt00L) by presenting itself as an official government results notification service. Users who subscribe expecting official government notifications are exposed to a third-party actor's channel under a false official identity. (location: page.html:295, page-text.txt:59)
hidden content
Inline CSS in the page body embeds <style> blocks directly inside <p> tags (page.html lines 698-723, 745-775), which is non-standard and used to inject styling outside the head. This technique can be used to hide or overlay content that is rendered differently by browsers versus scrapers/AI agents, and is consistent with cloaking or hidden content injection patterns. (location: page.html:698-723, page.html:745-775)
obfuscated code
The page contains a custom base64 encode/decode implementation (b2a, a2b, b64e, b64d functions) used by the Ad Inserter plugin to dynamically decode and inject ad code at runtime. The b64d function decodes base64-encoded content and injects it into the DOM via createContextualFragment, which is a common technique for hiding the true nature of injected code from static scanners. This appears in both the inline script block and the footer script block. (location: page.html:794-796, page-text.txt:794-796)
malicious redirect
Several internal navigation links and 'View More' buttons use HTTP (not HTTPS) URLs (e.g., http://sarkariresult.com.cm/result/, http://sarkariresult.com.cm/admit-card/) mixed with HTTPS canonical and og:url declarations. This HTTP/HTTPS inconsistency on a site presenting as an authoritative government portal could expose users to downgrade attacks or redirect interception, though this may also be a configuration oversight. (location: page.html:426, page.html:465, page.html:504, page.html:533)
curl https://api.brin.sh/domain/sarkariresult.com.cmCommon questions teams ask before deciding whether to use this domain in agent workflows.
sarkariresult.com.cm 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.