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.88235623.sbs' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds marketplace. The subdomain 'allegrolokalnie' directly mimics the legitimate brand 'Allegro Lokalnie' (lokalnie.allegro.pl), while using a suspicious numeric second-level domain '88235623.sbs' under the non-standard '.sbs' TLD — a classic typosquat/brand-impersonation pattern used to deceive users into believing they are on the official platform. (location: domain: allegrolokalnie.88235623.sbs)
phishing
The combination of a brand-impersonating subdomain (allegrolokalnie), a randomly-generated numeric SLD (88235623), and a non-standard TLD (.sbs) is a textbook phishing domain construction. TLS connection failed (connected=false, cert_valid=false), meaning the site either serves no valid certificate or is configured to avoid standard TLS inspection — consistent with a short-lived phishing page. The page content was not retrievable, which may indicate the site is geofenced, bot-detection-gated, or already taken down after credential harvesting. (location: domain: allegrolokalnie.88235623.sbs; TLS status: connected=false, cert_valid=false)
credential harvesting
Domains impersonating Allegro Lokalnie are routinely used in credential harvesting campaigns targeting Polish users, collecting login credentials and payment information. The failed TLS and empty page content suggest the site may be configured to only serve malicious content to targeted victims (e.g., via redirected links in SMS/email lures), further consistent with a credential harvesting operation. (location: domain: allegrolokalnie.88235623.sbs)
malicious redirect
The numeric SLD pattern (88235623.sbs) is associated with bulk-registered redirect/phishing infrastructure where multiple subdomains impersonate different brands under the same parent domain. This suggests the domain may be part of a larger phishing-as-a-service or redirect chain infrastructure. (location: domain: 88235623.sbs (parent SLD))
curl https://api.brin.sh/domain/allegrolokalnie.88235623.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.88235623.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.