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 domain 'allegrolokalnie.5rbkvdsjcjcj34b.sbs' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds platform. The subdomain 'allegrolokalnie' is a direct brand name copy hosted under a suspicious random-looking second-level domain '5rbkvdsjcjcj34b.sbs', a classic brand impersonation pattern used for phishing. (location: domain: allegrolokalnie.5rbkvdsjcjcj34b.sbs)
phishing
The URL structure combines a well-known Polish marketplace brand name (Allegro Lokalnie) with a randomly-generated-looking domain under the '.sbs' TLD, which is commonly abused for phishing campaigns. TLS is not connected and certificate is invalid, consistent with a hastily-deployed phishing site. (location: https://allegrolokalnie.5rbkvdsjcjcj34b.sbs)
credential harvesting
Sites impersonating Allegro Lokalnie are typically used to harvest login credentials and payment information from Polish e-commerce users. The combination of brand impersonation domain, invalid TLS, and unknown hosting strongly suggests a credential harvesting operation targeting Allegro Lokalnie users. (location: domain: allegrolokalnie.5rbkvdsjcjcj34b.sbs)
malicious redirect
The '.sbs' TLD combined with the random-looking domain string '5rbkvdsjcjcj34b' is characteristic of redirect chain infrastructure used in phishing kits, where users are funneled from spam/SMS links through intermediary domains to final credential-harvesting pages. TLS failure (connected=false) may indicate the page redirects or proxies to another host. (location: https://allegrolokalnie.5rbkvdsjcjcj34b.sbs)
social engineering
The domain is crafted to appear as a legitimate Allegro Lokalnie URL to Polish-speaking users, exploiting brand trust to deceive victims into believing they are on the official platform. This is a social engineering technique targeting users who may not scrutinize the full domain beyond the recognizable brand prefix. (location: domain: allegrolokalnie.5rbkvdsjcjcj34b.sbs)
curl https://api.brin.sh/domain/allegrolokalnie.5rbkvdsjcjcj34b.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.5rbkvdsjcjcj34b.sbs 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.