context safety score
A score of 48/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
brand impersonation
The domain 'internet-filiale.net' uses the German word 'filiale' (meaning 'branch' as in a bank or retail branch), combined with 'internet', strongly suggesting impersonation of a legitimate German-language banking or financial institution's online branch portal. This naming pattern is commonly used in phishing infrastructure targeting customers of German, Austrian, or Swiss banks. (location: domain: internet-filiale.net)
phishing
The domain 'internet-filiale.net' uses a .net TLD instead of a legitimate institution's .de or official TLD, combined with TLS failure (connected=false, cert_valid=false), indicating a likely phishing site that failed to load or is intermittently active. The domain construction mimics an online banking portal ('internet branch') which is a hallmark of financial phishing campaigns targeting German-speaking users. (location: domain: internet-filiale.net, metadata.json: tls.connected=false)
credential harvesting
The combination of a banking-themed domain name ('internet-filiale' = online branch), TLS certificate failure, and empty page content is consistent with a credential harvesting site — either temporarily inactive, behind a geo/IP filter, or in a setup/rotation phase. Such sites typically present fake login forms mimicking bank portals to steal usernames, passwords, and TANs. (location: domain: internet-filiale.net, metadata.json: tls.cert_valid=false)
curl https://api.brin.sh/domain/internet-filiale.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
internet-filiale.net currently scores 48/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.