context safety score
A score of 30/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
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
js obfuscation
Obfuscated document.write with encoded content
brand impersonation
The domain mypurecloud.de is serving a complete mirror of the official Genesys Cloud CX page (genesys.com/genesys-cloud). The page canonical URL, og:url, and all schema.org structured data point to www.genesys.com, not mypurecloud.de. The .de TLD is not an official Genesys domain listed in any hreflang or canonical tags on the page itself, indicating this is an unauthorized mirror impersonating the Genesys brand. (location: metadata.json: url=https://mypurecloud.de; page.html line 216: canonical href=https://www.genesys.com/genesys-cloud; og:url=https://www.genesys.com/genesys-cloud)
credential harvesting
The mirrored page includes a fully functional lead-capture form collecting extensive PII: work email, first name, last name, job level, job function, company name, telephone, country, state, website, city, job title, and industry. If mypurecloud.de is not operated by Genesys, this form submission data (routed through Oracle Eloqua with site ID 1260946616) could be intercepted or harvested by the domain operator. (location: page-text.txt lines 521-605; page.html Eloqua form integration)
phishing
The site presents itself as the legitimate Genesys Cloud CX platform including the Genesys logo, branding, product descriptions, pricing, and support contact information (888-GENESYS, +1 650 466-1100), while operating from an unofficial .de domain not listed in Genesys's own hreflang alternate URLs. Users or agents navigating to mypurecloud.de may believe they are on the official Genesys site and submit credentials or business information. (location: page.html lines 353-356 (Genesys logo), page-text.txt lines 625-628 (phone numbers), page.html line 22 (og:title Genesys))
malicious redirect
The language selector dropdown uses window.location.href to redirect users to www.genesys.com subpages (e.g., genesys.com/de-de/genesys-cloud) when switching languages, moving users from the unverified mypurecloud.de domain to the real genesys.com domain. While this specific behavior redirects to the legitimate site, it indicates the site operator has control over outbound navigation and could modify these redirects. (location: page.html line 1382: language-selector select onchange with window.location.href redirects to genesys.com)
curl https://api.brin.sh/domain/mypurecloud.deCommon questions teams ask before deciding whether to use this domain in agent workflows.
mypurecloud.de currently scores 30/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.