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 performs an immediate redirect (content='0; https://update-mobile-online.com') to an external domain, consistent with a scam/phishing landing page relay. The source comment explicitly labels this a 'DIRECT LINK SCAMPAGE' (GX40 toolkit). (location: page.html:14)
phishing
HTML comment header lists targeted email providers (Yahoo, Hotmail, Outlook, AOL, iCloud) and credits 'www.gx40sender.com', a known phishing/scampage kit distribution source. The page is explicitly labeled 'GX40 - DIRECT LINK SCAMPAGE' in the CSS comment. (location: page.html:2-10, page.html:27-28)
brand impersonation
The page favicon is set to the Apple logo from Wikimedia (Apple-Apple.svg), impersonating Apple to lend legitimacy to the redirect chain, consistent with Apple ID or iCloud credential harvesting campaigns. (location: page.html:13)
credential harvesting
The combination of Apple brand impersonation, targeted email provider list (iCloud, Yahoo, Hotmail, Outlook, AOL), and immediate redirect to 'update-mobile-online.com' is a classic credential harvesting relay pattern used to steal login credentials from victims of targeted phishing emails. (location: page.html:13-14)
hidden content
The visible page content is entirely blank (only 'Warten Sie Mal' — German for 'Just Wait' — as the title), while all malicious functionality is hidden in HTML comments and a meta refresh redirect. The page is designed to appear empty while silently redirecting victims. (location: page.html:24, page-text.txt:8)
social engineering
The page title 'Warten Sie Mal' (German: 'Just Wait') is a social engineering cue instructing victims to wait during the redirect, reducing suspicion while the malicious redirect executes. (location: page.html:24)
curl https://api.brin.sh/domain/jenhhivcs.web.appCommon questions teams ask before deciding whether to use this domain in agent workflows.
jenhhivcs.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.