context safety score
A score of 32/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
Domain 'klelnanzeigen-deutch.tz442x.life' is a typosquat of 'kleinanzeigen.de' (formerly eBay Kleinanzeigen), a major German classifieds platform. The misspelling ('kleln' instead of 'klein', 'deutch' instead of 'deutsch') is a classic typosquatting technique designed to deceive users who mistype or are redirected to this domain. (location: domain: klelnanzeigen-deutch.tz442x.life)
phishing
The domain combines a typosquatted brand name ('klelnanzeigen-deutch') with a suspicious registrar subdomain ('tz442x.life'). The '.life' TLD combined with a random-looking second-level domain ('tz442x') is a common pattern used in phishing infrastructure. The site failed TLS connection (connected=false, cert_valid=false), indicating either a newly stood-up phishing page or one that is selectively served. (location: domain: klelnanzeigen-deutch.tz442x.life, TLS: connected=false)
credential harvesting
Impersonation of Kleinanzeigen.de, a platform where users log in with credentials and conduct financial transactions, strongly suggests the purpose of this domain is credential harvesting — capturing usernames, passwords, and potentially payment information from victims who believe they are on the legitimate site. (location: domain: klelnanzeigen-deutch.tz442x.life)
malicious redirect
The subdomain structure (brand-typosquat.randomstring.life) is consistent with redirect infrastructure used in phishing campaigns, where victims are bounced through intermediary domains. The TLS failure may indicate the page only loads under specific referral or geotargeting conditions, a common evasion technique. (location: domain: klelnanzeigen-deutch.tz442x.life, hosting reputation: Unknown)
curl https://api.brin.sh/domain/klelnanzeigen-deutch.tz442x.lifeCommon questions teams ask before deciding whether to use this domain in agent workflows.
klelnanzeigen-deutch.tz442x.life currently scores 32/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.