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 (delay=0) to 'https://miles-more-sicherheit.com/service/', a suspicious external domain unrelated to the hosting domain. This is a classic scampage redirect technique used to send victims to a credential harvesting or phishing page while using a trusted hosting platform (Firebase) as a launchpad. (location: page.html:14 - <meta content='0; https://miles-more-sicherheit.com/service/' http-equiv='refresh'/>)
brand impersonation
The page uses an Apple logo (Apple SVG from Wikimedia) as the favicon, impersonating Apple Inc. to deceive victims into believing the page or destination is Apple-affiliated. Combined with the redirect, this is consistent with Apple ID phishing infrastructure. (location: page.html:13 - <link href='https://upload.wikimedia.org/wikipedia/commons/thumb/d/df/Apple-Apple.svg/1000px-Apple-Apple.svg.png' rel='icon'/>)
phishing
The page is explicitly self-identified in its source code as a 'DIRECT LINK SCAMPAGE' built with the GX40 phishing kit (sourced from www.gx40sender.com). The GX40 kit is a known phishing tool targeting major email providers including Yahoo, Hotmail/Outlook, AOL, and iCloud/Apple. The page acts as a redirect stub that funnels victims to the actual credential harvesting page. (location: page.html:2-10 (HTML comment) and page.html:27 (CSS comment: 'GX40 - DIRECT LINK SCAMPAGE'))
credential harvesting
The GX40 kit comment explicitly lists targeted credential sources: Yahoo, Hotmail & Outlook, AOL, and iCloud. The redirect destination (miles-more-sicherheit.com/service/) is the likely credential harvesting endpoint. The infrastructure pattern — trusted cloud host as redirect stub, external domain as harvester — is designed to evade blocklists and email security filters. (location: page.html:3-8 (HTML comment listing targeted email/account providers))
hidden content
The visible page text is entirely blank (only whitespace and the title 'Warten Sie Mal', German for 'Just a moment'). All malicious intent is concealed within HTML comments and a meta-refresh redirect, with no visible content to alert the victim or security scanners performing surface-level text analysis. (location: page-text.txt:1-10 (empty visible content); page.html:2-10 and page.html:25-29 (obfuscated intent in comments))
social engineering
The page title 'Warten Sie Mal' (German: 'Just a moment' or 'Wait a second') is a social engineering lure designed to make victims expect a brief loading delay before being silently redirected, suppressing suspicion during the redirect chain. (location: page.html:24 - <title>Warten Sie Mal</title>)
curl https://api.brin.sh/domain/gawhybnoc.firebaseapp.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
gawhybnoc.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.