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.9028512.sbs' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds platform (allegro.pl / allegrolokalnie.pl). The subdomain-style prefix 'allegrolokalnie' combined with a numeric subdomain '9028512' under the suspicious TLD '.sbs' is a classic brand impersonation pattern designed to deceive users into believing they are visiting the legitimate Allegro Lokalnie service. (location: domain: allegrolokalnie.9028512.sbs)
phishing
The domain structure — a well-known brand name ('allegrolokalnie') prefixed to a numeric subdomain under a low-reputation TLD ('.sbs') — is consistent with phishing infrastructure. The TLS connection failed entirely (connected=false, cert_valid=false), which is characteristic of phishing pages that may serve content over HTTP or have misconfigured HTTPS, reducing user trust signals while still harvesting credentials or data. (location: domain: allegrolokalnie.9028512.sbs, TLS: connected=false)
credential harvesting
Allegro Lokalnie is a login-required marketplace platform. A site impersonating this brand is highly likely to present a fake login form to harvest Polish users' Allegro account credentials (username/password), which can then be used for account takeover, fraud, or resale. (location: domain: allegrolokalnie.9028512.sbs)
social engineering
The use of a recognizable brand name ('allegrolokalnie') as the apparent subdomain exploits user familiarity and trust in the Allegro Lokalnie brand. Users may be socially engineered via phishing emails or SMS messages containing this link, believing it to be a legitimate Allegro Lokalnie URL, especially less technically savvy users who do not scrutinize full domain names. (location: domain: allegrolokalnie.9028512.sbs)
malicious redirect
The numeric subdomain pattern '9028512.sbs' is commonly associated with redirect/hosting infrastructure used by phishing kit operators to serve multiple campaigns from a single hosting provider. The page content could not be retrieved (empty HTML/text), suggesting the site may be gated, performing user-agent or geo-based redirection, or currently inactive between phishing campaign waves. (location: domain: allegrolokalnie.9028512.sbs, page.html: empty, page-text.txt: empty)
curl https://api.brin.sh/domain/allegrolokalnie.9028512.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.9028512.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.