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
Page uses both a meta refresh tag and a JavaScript window.location redirect to send users to a suspicious third-party domain 'fram9hkkm3urfzeqa3f8070221ro047432.nl' targeting a path '/file/wetransfer.html'. The randomized subdomain-style domain is characteristic of phishing infrastructure. (location: page.html:5-8)
brand impersonation
The domain 'wetransconect-71216.firebaseapp.com' impersonates WeTransfer (the legitimate file-sharing service) via a misspelling ('wetransconect' vs 'wetransfer'). The redirect destination path '/file/wetransfer.html' and the visible anchor tag linking to 'https://wetransfer.com/' reinforce the WeTransfer brand impersonation. (location: page.html:7,13; metadata.json:domain)
phishing
The page is a phishing redirect page hosted on Firebase, impersonating WeTransfer. It silently redirects users to a suspicious .nl domain hosting a fake WeTransfer page, likely to harvest credentials or deliver malware. The visible text in French ('Vous allez être redirigé vers votre Espace Personnel') is a social lure implying a personal account area. (location: page.html:5-13)
social engineering
Visible body text in French tells users they are being redirected to their 'Espace Personnel' (Personal Space/Account), creating a false sense of legitimacy and urgency to follow through with the redirect to the malicious domain. (location: page.html:13; page-text.txt:3)
hidden content
The anchor tag linking to 'https://wetransfer.com/' has no visible link text (empty anchor), creating a hidden link to the legitimate WeTransfer site. This may be used to create a superficial association with the legitimate brand while the actual redirect goes elsewhere, or to evade automated scanners that check for legitimate brand links. (location: page.html:13)
curl https://api.brin.sh/domain/wetransconect-71216.firebaseapp.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
wetransconect-71216.firebaseapp.com 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.