context safety score
A score of 30/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 'allegrolokalnie.83921.cyou' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds platform. The subdomain string 'allegrolokalnie' directly mimics the legitimate brand 'Allegro Lokalnie' (lokalnie.allegro.pl), hosted under a suspicious .cyou TLD with a numeric second-level domain '83921.cyou', a classic typosquatting and brand-abuse pattern used to deceive users into believing they are on the legitimate Allegro Lokalnie site. (location: domain: allegrolokalnie.83921.cyou)
phishing
The domain structure (brand name + suspicious registrar-style numeric .cyou TLD) is consistent with a phishing site targeting Allegro Lokalnie users. TLS connection failed (connected=false, cert_valid=false), meaning the site either serves no content or uses an invalid certificate, both common in short-lived phishing infrastructure. The combination of brand impersonation domain, failed TLS, and unknown hosting strongly indicates a phishing operation. (location: domain: allegrolokalnie.83921.cyou, metadata.json TLS fields)
credential harvesting
Sites impersonating Allegro Lokalnie typically present fake login pages to harvest Polish user credentials (email/password) and payment details. The domain pattern matches known Allegro phishing campaigns that redirect users to credential-capture forms. No page content was retrievable, consistent with evasion techniques (bot/scanner blocking) used by credential harvesting pages. (location: domain: allegrolokalnie.83921.cyou)
malicious redirect
The .cyou TLD with numeric SLD ('83921.cyou') is a known pattern used by redirect chains and traffic distribution systems (TDS). The site may serve as a redirect node routing victims to downstream phishing or malware pages based on geolocation or user-agent. Failed TLS and empty page content suggest the page may only render for targeted victims. (location: domain: allegrolokalnie.83921.cyou, metadata.json)
curl https://api.brin.sh/domain/allegrolokalnie.83921.cyouCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.83921.cyou currently scores 30/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.