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 to 'https://telekom.242221.com' (content='0; https://telekom.242221.com'). The destination domain is a lookalike/scam domain impersonating Deutsche Telekom using a numeric subdomain, designed to send victims to a phishing or credential harvesting page. (location: page.html:14)
brand impersonation
The page uses an Apple logo (Apple SVG from Wikimedia) as the favicon while the redirect targets a Telekom-impersonating domain. This multi-brand deception targets Apple and Telekom users simultaneously to lower suspicion and appear legitimate. (location: page.html:13)
phishing
HTML comment explicitly labels this as a 'GX40 - DIRECT LINK SCAMPAGE' and lists targeted email providers: Yahoo, Hotmail, Outlook, AOL, iCloud. This is a purpose-built phishing kit landing page designed to harvest credentials from users of these services. (location: page.html:2-10)
credential harvesting
The page is attributed to 'www.gx40sender.com', a known phishing kit/scampage toolkit. The listed target platforms (Yahoo, Hotmail/Outlook, AOL, iCloud) are all major email/credential providers, indicating this page is the entry point of a credential harvesting campaign. (location: page.html:8)
social engineering
The visible page title is 'Seite wird geladen...' (German: 'Page is loading...'), presenting a fake loading screen to mask the immediate redirect. This deceptive UX is designed to prevent victims from noticing they are being silently redirected to a scam site. (location: page.html:24, page-text.txt:8)
hidden content
The page body contains no visible content — only blank lines and the fake loading title. All malicious logic is embedded in the HTML head (meta refresh redirect, Apple favicon spoofing) and HTML comments, making the threat invisible to casual inspection and potentially bypassing simple content scanners. (location: page.html:1-31, page-text.txt:1-10)
curl https://api.brin.sh/domain/zuwmbztn.web.appCommon questions teams ask before deciding whether to use this domain in agent workflows.
zuwmbztn.web.app 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.