context safety score
A score of 34/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 'allegrolokalnie.90233.cyou' directly impersonates 'Allegro Lokalnie' (allegro.pl), a major Polish e-commerce and classifieds platform. The subdomain replicates the brand name exactly while hosted on a suspicious .cyou TLD under a numeric throwaway domain (90233.cyou), a classic typosquat/brand-abuse pattern used to deceive users into believing they are on a legitimate Allegro property. (location: domain: allegrolokalnie.90233.cyou)
phishing
The combination of exact brand-name impersonation ('allegrolokalnie') on a non-legitimate TLD (.cyou) with invalid TLS and unknown hosting is consistent with a phishing infrastructure targeting Allegro Lokalnie users. Such domains are routinely used to harvest login credentials or payment data from victims expecting the real Allegro Lokalnie site. (location: domain: allegrolokalnie.90233.cyou)
credential harvesting
Domains impersonating Allegro Lokalnie are frequently used in Polish-language phishing campaigns that present fake login or payment forms to harvest user credentials and financial information. The invalid TLS certificate (connected=false, cert_valid=false) suggests the site may not load over HTTPS properly, a common trait of hastily deployed credential-harvesting pages. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
malicious redirect
The page content was empty at scan time, which may indicate the site performs server-side or JavaScript-based cloaking, serving benign or empty content to scanners while redirecting real users to a phishing or malware page. This cloaking behavior is a known evasion technique used by malicious redirect infrastructure. (location: page.html (empty), page-text.txt (empty))
curl https://api.brin.sh/domain/allegrolokalnie.90233.cyouCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.90233.cyou currently scores 34/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.