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
Immediate meta refresh redirect (0 seconds) to 'https://kontovalidierung.xyz/Login' — a suspicious third-party domain with a German-language login path ('kontovalidierung' = 'account validation'), strongly indicating a credential harvesting landing page. (location: page.html:14 — <meta content='0; https://kontovalidierung.xyz/Login' http-equiv='refresh'/>)
credential harvesting
The redirect destination 'kontovalidierung.xyz/Login' translates to 'account validation' in German and targets a /Login endpoint, consistent with a fake login page designed to steal user credentials. (location: page.html:14 — redirect target https://kontovalidierung.xyz/Login)
brand impersonation
The page favicon is set to Apple's official logo from Wikimedia Commons, impersonating Apple to build false trust before redirecting victims to a credential harvesting site. (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
HTML comment explicitly labels this as a 'GX40 - DIRECT LINK SCAMPAGE' and lists targeted email providers (Yahoo, Hotmail, Outlook, AOL, iCloud), confirming this is a purpose-built phishing kit page. Source attributed to 'www.gx40sender.com'. (location: page.html:2-10 — HTML comment block and page.html:27 — CSS comment 'GX40 - DIRECT LINK SCAMPAGE')
social engineering
Page title 'Warten Sie Mal' (German: 'Wait a Moment') is a social engineering delay tactic displayed while the invisible redirect executes, preventing user suspicion during the redirection. (location: page.html:24 — <title>Warten Sie Mal</title> and page-text.txt:8)
hidden content
The visible page content is entirely blank/empty (only whitespace in page-text.txt) while the real malicious activity (redirect to phishing login) happens invisibly via meta refresh, deliberately hiding the page's true purpose from users. (location: page-text.txt:1-10 — no visible content rendered to user)
curl https://api.brin.sh/domain/wiziftonyq.firebaseapp.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
wiziftonyq.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.