context safety score
A score of 42/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
phishing
Domain 'inflowwapi.com' uses a doubled letter ('ww') in what appears to be an 'inflow api' brand name, a classic typosquatting/homoglyph technique used to impersonate legitimate API or SaaS services and deceive users or automated agents into trusting the domain. (location: metadata.json: domain field)
brand impersonation
The domain 'inflowwapi.com' mimics a legitimate 'inflow API' or similar branded API service via character duplication ('infloww' vs 'inflow'), a common brand impersonation pattern used to intercept API traffic or credentials from developers and AI agents. (location: metadata.json: domain field)
malicious redirect
TLS connection failed (connected=false, cert_valid=false, san_match=false) yet the URL uses the https:// scheme. This misconfiguration or intentional TLS failure may be used to downgrade connections, perform MITM attacks, or redirect traffic insecurely. Legitimate API endpoints do not fail TLS validation. (location: metadata.json: tls object)
credential harvesting
The combination of an API-themed domain name ('inflowwapi.com'), failed TLS (no valid certificate), and completely empty page content is consistent with a credential harvesting or API key interception endpoint — designed to silently accept and log credentials or tokens submitted by clients without serving any legitimate content. (location: metadata.json and page.html (empty))
hidden content
The page returns no visible content (page-text.txt empty), no HTML (page.html empty), and no hidden elements (page-hidden.txt empty), while the domain is actively registered and resolves. A deliberately blank but reachable endpoint is a common technique to avoid automated content scanners while still functioning as a data collection or redirect backend. (location: page.html, page-text.txt, page-hidden.txt (all empty))
curl https://api.brin.sh/domain/inflowwapi.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
inflowwapi.com currently scores 42/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.