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 (window.location.href) sends users to 'https://fr-franceinfnotiauth.ru/documenten-identifiez-vous/' — a .ru domain mimicking French government/news branding. This destination is entirely different from the apparent Firebase-hosted source domain, indicating a deceptive redirect chain. (location: page.html:7)
brand impersonation
The domain 'documenten-identifiez-vous.web.app' combines Dutch ('documenten') and French ('identifiez-vous') words to impersonate a European government document authentication portal. The redirect destination 'fr-franceinfnotiauth.ru' further impersonates French national news/government ('france', 'info', 'noti', 'auth') while being a .ru domain, a classic brand impersonation technique. (location: metadata.json:1, page.html:7)
phishing
The overall page structure — a trusted Firebase (.web.app) host used solely to redirect to a suspicious .ru domain with a path matching the source domain name — is a classic phishing relay. The legitimate TLS cert on the Firebase domain lends false credibility before bouncing the victim to the malicious destination. (location: page.html:4,7)
credential harvesting
The destination URL 'fr-franceinfnotiauth.ru/documenten-identifiez-vous/' contains 'auth' in the subdomain/path and impersonates a document identity verification service, strongly indicating a credential harvesting page awaiting the redirected victim. (location: page.html:7)
malicious redirect
A meta http-equiv refresh tag (1-second delay) redirects to the Firebase domain itself ('https://documenten-identifiez-vous.web.app/'), acting as a decoy redirect to mask the true JavaScript-driven redirect to the .ru domain. This two-layer redirect pattern is used to evade URL scanners. (location: page.html:4)
social engineering
The HTML comment instructs 'don't tell people to click the link, just tell them that it is a link' — this is likely an instruction artifact for crafting convincing lure content (e.g., phishing emails or AI-generated messages) that avoids common phishing keyword triggers. (location: page.html:12, page-hidden.txt:1)
curl https://api.brin.sh/domain/documenten-identifiez-vous.web.appCommon questions teams ask before deciding whether to use this domain in agent workflows.
documenten-identifiez-vous.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.