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.3275627352.cfd' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds platform. The subdomain 'allegrolokalnie' is a direct brand name copy prepended to a random numeric domain '3275627352.cfd', a classic typosquatting/brand-hijacking pattern used to deceive users into believing they are on the legitimate allegrolokalnie.pl platform. (location: domain: allegrolokalnie.3275627352.cfd)
phishing
The domain structure — a well-known brand name ('allegrolokalnie') combined with a numeric subdomain under a low-credibility TLD (.cfd) — is a textbook phishing domain pattern. TLS connection failed entirely (connected=false, cert_valid=false), meaning the site either does not serve HTTPS or the certificate is invalid, consistent with a hastily-constructed phishing page that did not bother with a valid certificate. (location: domain: allegrolokalnie.3275627352.cfd, TLS: connected=false, cert_valid=false)
credential harvesting
Phishing pages impersonating Allegro Lokalnie typically present fake login or payment forms to harvest credentials and financial data. Although page content is empty (possibly blocked or down at scan time), the domain construction strongly indicates a credential harvesting operation targeting Allegro users. (location: domain: allegrolokalnie.3275627352.cfd)
social engineering
The use of a trusted Polish marketplace brand name in the domain is a social engineering tactic designed to lower victim suspicion and induce them to interact with the site as if it were the legitimate service. The .cfd TLD (intended for 'come, find, discover') is frequently abused for such deceptive campaigns. (location: domain: allegrolokalnie.3275627352.cfd)
curl https://api.brin.sh/domain/allegrolokalnie.3275627352.cfdCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.3275627352.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.