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
Page immediately redirects via both meta http-equiv refresh and JavaScript window.location.href to https://auth.neuesupdates-id.de/milesmore/ — a suspicious lookalike domain designed to appear as a legitimate authentication or update service. The redirect fires at content='0' (instant) leaving no visible page content. (location: page.html:4-8)
brand impersonation
The destination domain 'neuesupdates-id.de' combines 'neue' (German: new), 'updates', and 'id' to impersonate a legitimate identity/authentication or software update authority. The path '/milesmore/' likely targets Miles & More, the Lufthansa Group loyalty program, constituting brand impersonation of both an update/auth service and the Miles & More frequent flyer program. (location: page.html:4,7)
phishing
The redirect to https://auth.neuesupdates-id.de/milesmore/ is consistent with a credential harvesting phishing campaign targeting Miles & More loyalty program members. The subdomain 'auth.' is used to add false legitimacy and trick users into entering login credentials. (location: page.html:4,7)
credential harvesting
The combination of an 'auth.' subdomain, an 'id' component in the domain, and the '/milesmore/' path strongly indicates a fake authentication page designed to harvest Miles & More account credentials (username, password, and potentially payment or loyalty point data). (location: page.html:4,7)
social engineering
The page is titled 'Page Redirection' to normalize the redirect behavior for any user who might notice it, reducing suspicion and increasing the likelihood that victims will proceed to the phishing destination without questioning the navigation. (location: page.html:9)
hidden content
The page-text.txt is completely empty, confirming there is no visible content presented to the user before the instant redirect occurs. All malicious activity is concealed in meta and script tags with no user-visible indication of the true destination. (location: page.html:1-10)
curl https://api.brin.sh/domain/zqdtiuqvbzzjf.web.appCommon questions teams ask before deciding whether to use this domain in agent workflows.
zqdtiuqvbzzjf.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.