context safety score
A score of 45/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 loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
credential harvesting
JavaScript code reads the user's email address from browser cookies and pushes it to the Google Tag Manager dataLayer on specific pages ('earn-more', 'notification', and language-variant pages). This harvests email credentials from cookies and sends them to third-party analytics infrastructure without clear user consent disclosure. (location: page.html lines 48-75, page-text.txt lines 36-64)
social engineering
Page uses high-pressure, reward-focused language ('Get Up To $5 Per Answer', 'Start earning in 73 seconds', 'Cash out via PayPal') designed to entice users into registering and providing personal and financial account information (PayPal email). The instruction to 'Register with the same email you are using for your PayPal account' directly links sign-up to financial account details. (location: page-text.txt line 1 (visible content section))
credential harvesting
Sign-up flow explicitly instructs users to register with their PayPal account email address, effectively harvesting a financial account identifier at registration. Combined with the cookie email exfiltration scripts, this creates a pipeline from registration email to analytics data layer. (location: page-text.txt line 1 (visible content: 'Register with the same email you are using for your PayPal account'))
hidden content
Google Tag Manager noscript iframe (0x0, display:none, visibility:hidden) and Facebook Pixel noscript tracking image (1x1, display:none) load silently without visible user notification, enabling covert cross-site tracking and data collection. (location: page.html lines 12-13, page-text.txt lines 1-2)
curl https://api.brin.sh/domain/survimo.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
survimo.com currently scores 45/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.