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
The subdomain 'allegrolokalnie.b8c12.top' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds platform. The legitimate domain is allegrolokalnie.pl; this site uses a lookalike subdomain on a suspicious TLD (.top) under the unrelated base domain b8c12.top to deceive users into believing they are visiting the real Allegro Lokalnie service. (location: domain: allegrolokalnie.b8c12.top)
phishing
The domain construction (brand name as subdomain on a random-looking base domain with .top TLD) is a classic phishing pattern used to impersonate established brands. The TLS certificate is invalid and the connection failed, consistent with a hastily deployed phishing infrastructure. The combination of brand impersonation subdomain, non-functional TLS, and unknown hosting strongly indicates a phishing operation targeting users of Allegro Lokalnie. (location: url: https://allegrolokalnie.b8c12.top, tls.connected=false, tls.cert_valid=false)
credential harvesting
Sites impersonating Allegro Lokalnie (a marketplace requiring user login) are typically deployed to harvest credentials (username/password) or payment information from victims who believe they are logging into the legitimate platform. The phishing infrastructure pattern supports this as the likely end goal. (location: domain: allegrolokalnie.b8c12.top)
social engineering
The use of the full brand name 'allegrolokalnie' as the subdomain is a deliberate social engineering technique to create false legitimacy and trust, exploiting users' familiarity with the real Allegro Lokalnie brand to lower their guard before credential or payment data theft. (location: domain: allegrolokalnie.b8c12.top)
curl https://api.brin.sh/domain/allegrolokalnie.b8c12.topCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.b8c12.top 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.