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 (0 seconds) to 'https://konto-registrierung.online/login/' — a suspicious domain with German-language path ('konto-registrierung' means 'account registration') consistent with a credential harvesting landing page. (location: page.html:14)
credential harvesting
The redirect destination 'konto-registrierung.online/login/' is a likely fake login/account-registration page designed to steal credentials. The domain name translates to 'account-registration' in German and leads to a /login/ endpoint, a classic credential phishing pattern. (location: page.html:14)
brand impersonation
The page uses an Apple logo (Apple-Apple.svg from Wikimedia) as the favicon while the HTML comment explicitly lists targeted email providers: Yahoo, Hotmail, Outlook, AOL, iCloud. This impersonates Apple/iCloud and major email brands to lend legitimacy before redirecting victims. (location: page.html:13)
phishing
HTML comments identify this as a 'GX40 - DIRECT LINK SCAMPAGE' sourced from 'www.gx40sender.com', a known phishing kit distribution source. The page is an intermediary scam page explicitly targeting multiple email provider accounts (Yahoo, Hotmail/Outlook, AOL, iCloud). (location: page.html:2-10, page.html:27-28)
social engineering
Page title 'Warten Sie Mal' (German for 'Wait a moment') is a social engineering tactic to make the victim passively wait during the redirect, reducing suspicion while the malicious redirect executes. (location: page.html:24, page-text.txt:8)
hidden content
The visible page content is almost entirely blank (only the title text 'Warten Sie Mal' is rendered). All malicious logic — the redirect, brand impersonation favicon, and kit attribution — is hidden from the user's view, concealing the page's true purpose. (location: page-text.txt:1-10)
obfuscated code
The page is structured as a Blogger/GML template (using xmlns:b, b:skin, b:if, expr: attributes) deployed on Firebase, obscuring its true purpose as a phishing redirect page. Using a legitimate hosting platform (Firebase/Google) and a blog template framework serves to evade automated URL scanners and blocklists. (location: page.html:11, metadata.json:1)
curl https://api.brin.sh/domain/jgqshpywuke.firebaseapp.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
jgqshpywuke.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.