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
The domain 'allegrolokalnie.78349754.sbs' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds platform (allegro.pl). The subdomain 'allegrolokalnie' directly mimics the legitimate brand name while hosted under a suspicious numeric third-level domain on the '.sbs' TLD, a pattern characteristic of typosquatting and brand impersonation fraud. (location: domain: allegrolokalnie.78349754.sbs)
phishing
The domain structure combines brand impersonation of a well-known Polish marketplace (Allegro Lokalnie) with a randomly-generated numeric second-level domain (.78349754.sbs), which is a hallmark of phishing infrastructure. The TLS connection failure (connected=false, cert_valid=false) indicates the site may be serving content without valid HTTPS, consistent with hastily deployed phishing pages. (location: domain: allegrolokalnie.78349754.sbs, TLS metadata)
credential harvesting
Combination of brand impersonation of a major e-commerce platform, invalid/missing TLS certificate, and use of a throwaway numeric domain strongly indicates credential harvesting targeting users of Allegro Lokalnie who may enter login credentials, payment details, or personal information believing they are on the legitimate platform. (location: domain: allegrolokalnie.78349754.sbs, metadata.json TLS fields)
malicious redirect
The '.sbs' TLD combined with a numeric registrable domain (78349754.sbs) is frequently used as a redirect or parking layer in phishing chains. The page content returned empty, which may indicate the active payload is gated behind redirects, user-agent checks, or geographic filters not triggered during this scan. (location: domain: allegrolokalnie.78349754.sbs, page.html (empty response))
curl https://api.brin.sh/domain/allegrolokalnie.78349754.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.78349754.sbs 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.