context safety score
A score of 47/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
cloaking
Page conditionally redirects based on referrer or user-agent
brand impersonation
The site sarahah.pro uses the name, logo, and branding of the original Sarahah anonymous messaging platform (sarahah.com), including identical Arabic branding 'صراحة Sarahah', mirrored UI layout, and social media handles (@sarahah_pro). The .pro TLD with near-identical branding is a classic typosquatting/brand-impersonation pattern designed to deceive users familiar with the original service. (location: page.html: <title>, <h1>, og:title, logo_nav.png, og:image, meta keywords including 'sarahah', 'sarahah2')
credential harvesting
The site presents login ('دخول') and registration ('حساب جديد') entry points on a domain impersonating the legitimate Sarahah platform. Users who believe they are on the real service may submit credentials to this third-party site, enabling credential harvesting. (location: page.html: <a href='login'>, <a href='register'>)
social engineering
On Android devices, a JavaScript confirm() dialog is triggered after 2 seconds prompting users to download an app from the Google Play Store (id=app.sarhne.com). The message ('للمتابعة بشكل افضل حمل تطبيق صراحه') pressures users to install a third-party app under the guise of a better experience, which may be a malicious or data-harvesting application. (location: page.html: <script> window.onload Android detect + confirm() redirect to play.google.com/store/apps/details?id=app.sarhne.com&ref=sarahah.pro)
malicious redirect
Android users are automatically redirected to a Google Play app (app.sarhne.com) via a timed JavaScript confirm dialog. The app ID 'app.sarhne.com' does not correspond to the original Sarahah app and may be a copycat or malicious application designed to harvest user data. (location: page.html: location.href='https://play.google.com/store/apps/details?id=app.sarhne.com&ref=sarahah.pro')
curl https://api.brin.sh/domain/sarahah.proCommon questions teams ask before deciding whether to use this domain in agent workflows.
sarahah.pro currently scores 47/100 with a suspicious 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.