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.387328752.cfd' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds platform. The subdomain 'allegrolokalnie' directly mimics the legitimate brand name 'Allegro Lokalnie' (allegrolokalnie.pl), hosted under a suspicious numeric second-level domain '387328752.cfd' using a low-trust TLD (.cfd), a classic typosquatting/brand-impersonation pattern used in phishing campaigns targeting Polish users. (location: domain: allegrolokalnie.387328752.cfd)
phishing
The domain structure — brand name ('allegrolokalnie') combined with a randomized numeric domain ('387328752') under the .cfd TLD — is a well-established phishing pattern. The .cfd TLD (coming from 'certified') is heavily abused for phishing. Combined with TLS connection failure (connected=false, cert_valid=false), this strongly indicates a phishing site that may have gone offline or is intermittently active, consistent with short-lived phishing infrastructure. (location: domain: allegrolokalnie.387328752.cfd; metadata.json tls block)
social engineering
Impersonating 'Allegro Lokalnie', a trusted Polish marketplace, is a social engineering vector designed to trick users into believing they are on a legitimate platform. Users expecting to interact with a known brand would be primed to enter credentials, payment details, or personal information without suspicion. (location: domain: allegrolokalnie.387328752.cfd)
credential harvesting
Domains impersonating Allegro Lokalnie are routinely used to harvest login credentials and payment information from Polish marketplace users. Although page content was not retrievable (empty HTML/text), the domain pattern is consistent with credential harvesting infrastructure observed in Polish e-commerce phishing campaigns. (location: domain: allegrolokalnie.387328752.cfd; page.html (empty — site unreachable or content blocked))
curl https://api.brin.sh/domain/allegrolokalnie.387328752.cfdCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.387328752.cfd 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.