context safety score
A score of 43/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
Meta refresh tag immediately redirects visitors to 'https://xhymtouaqvkwsve-sicherheit.de/postbank/' — a domain impersonating Postbank (German bank) at a suspicious unrelated domain, consistent with a phishing relay page. (location: page.html:14)
phishing
The redirect destination '/postbank/' path combined with the German-language title 'Warten Sie Mal' (Wait a moment) and the redirect infrastructure strongly indicates this is a Postbank credential-harvesting phishing page using a Firebase-hosted relay. (location: page.html:14, page.html:24)
brand impersonation
Apple favicon loaded from Wikimedia Commons ('Apple-Apple.svg') to impersonate Apple branding on what is a banking phishing relay, creating false legitimacy and confusing victims about the site's identity. (location: page.html:13)
brand impersonation
The redirect targets '/postbank/' path, impersonating Postbank (Deutsche Bank subsidiary), a major German financial institution, to harvest banking credentials. (location: page.html:14)
credential harvesting
Site is a scampage relay (self-identified as 'GX40 - DIRECT LINK SCAMPAGE' in embedded CSS comment) designed to forward victims to a credential-harvesting phishing page targeting banking customers. (location: page.html:27)
hidden content
HTML comment block at the top of the page reveals scampage toolkit infrastructure: 'GX40 - LET'S SHOW THE CODE', listing targeted email providers (Yahoo, Hotmail, Outlook, AOL, iCloud) and source attribution to 'www.gx40sender.com', a known phishing kit distribution site. This metadata is hidden from victims. (location: page.html:2-10)
social engineering
Page title 'Warten Sie Mal' (German: 'Wait a moment') is a social engineering tactic to keep victims on the page during the redirect delay, reducing suspicion while the malicious redirect executes. (location: page.html:24)
obfuscated code
The page uses a Firebase-hosted subdomain with a randomized name ('putzvneaumqi-bohfrgzkfexn.firebaseapp.com') as an intermediary relay to obscure the true phishing destination and evade blocklists that target the final phishing domain directly. (location: metadata.json:1, page.html:14)
curl https://api.brin.sh/domain/putzvneaumqi-bohfrgzkfexn.firebaseapp.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
putzvneaumqi-bohfrgzkfexn.firebaseapp.com currently scores 43/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.