context safety score
A score of 47/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
JavaScript redirect to 'https://fr.gonnecxionne-loundingcharge.shop/bnpcacao/postale' — a typosquatting domain mimicking BNP (French bank) with path 'bnpcacao/postale' suggesting a banking/postal phishing landing page. The domain 'gonnecxionne-loundingcharge.shop' uses a .shop TLD and obfuscated branding to evade detection. (location: page.html:7 — window.location.href)
brand impersonation
The redirect target path '/bnpcacao/postale' and domain fragment 'gonnecxionne' strongly suggest impersonation of BNP Paribas (major French bank) and/or La Poste (French postal service), both commonly targeted in French-language credential harvesting campaigns. (location: page.html:7 — redirect URL path '/bnpcacao/postale')
phishing
The full redirect chain (innocuous Firebase hosting page → suspicious .shop domain with banking/postal path) is a classic phishing delivery mechanism: the origin URL appears benign while the actual malicious content is hosted at the redirect destination. (location: page.html:5,7 — meta refresh and JS redirect)
malicious redirect
Meta http-equiv refresh tag redirects to 'http://whouaquessequesais.web.app' (insecure HTTP, not HTTPS), creating a protocol downgrade from the HTTPS origin. This may be used to strip TLS protections or serve different content to crawlers vs. real users. (location: page.html:5 — meta http-equiv='refresh')
social engineering
The page presents itself as a benign 'Page Redirection' with fallback link text to 'example.com', masking the true destination. This is designed to reassure users and automated scanners while silently redirecting victims to a malicious site. (location: page.html:9,13 — title and anchor text)
curl https://api.brin.sh/domain/whouaquessequesais.web.appCommon questions teams ask before deciding whether to use this domain in agent workflows.
whouaquessequesais.web.app currently scores 47/100 with a suspicious verdict and medium 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.