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.52489602342096554.sbs' directly incorporates 'allegrolokalnie', mimicking the legitimate Polish e-commerce platform Allegro Lokalnie (allegrolokalnie.pl). The use of a random numeric subdomain (52489602342096554) under a suspicious .sbs TLD is a classic typosquatting/brand impersonation pattern used to deceive users into believing they are on the official Allegro platform. (location: domain: allegrolokalnie.52489602342096554.sbs)
phishing
The domain structure — brand name + long numeric string + uncommon TLD (.sbs) — is a well-established phishing infrastructure pattern. The TLS connection failed (connected=false, cert_valid=false), meaning the site either serves no valid HTTPS or uses an invalid certificate, consistent with a hastily deployed phishing page targeting Allegro Lokalnie users. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
Impersonation of Allegro Lokalnie combined with failed TLS and an opaque hosting provider strongly suggests a credential harvesting operation. Allegro Lokalnie users may be lured to this domain and prompted to enter their login credentials, payment details, or personal information under the false impression they are on the legitimate marketplace. (location: domain: allegrolokalnie.52489602342096554.sbs, metadata.json: hosting.reputation=Unknown)
social engineering
The domain name is crafted to exploit user trust in the Allegro Lokalnie brand. Polish consumers familiar with 'allegrolokalnie.pl' may be socially engineered via phishing emails, SMS, or search ads to visit this lookalike domain, particularly for transaction-related lures (e.g., fake payment requests, parcel tracking, or account verification). (location: domain: allegrolokalnie.52489602342096554.sbs)
curl https://api.brin.sh/domain/allegrolokalnie.52489602342096554.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.52489602342096554.sbs 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.