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.9423021.sbs' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds marketplace. The subdomain 'allegrolokalnie' is a direct clone of the legitimate brand name 'Allegro Lokalnie' (lokalnie.allegro.pl), hosted under a numeric subdomain registrar abuse pattern ('9423021.sbs'). This is a classic brand-squatting technique used in phishing campaigns targeting Polish users. (location: domain: allegrolokalnie.9423021.sbs)
phishing
The domain combines brand impersonation of a well-known Polish marketplace (Allegro Lokalnie) with a suspicious TLD (.sbs) and a numeric second-level domain (9423021.sbs), a pattern strongly associated with phishing infrastructure. TLS connection failed entirely (connected=false, cert_valid=false), indicating the site may be non-functional, taken down, or using non-standard delivery — consistent with a phishing page lifecycle. The domain age of 3816 days for the registrar/SLD does not correspond to the subdomain, which is likely newly created. (location: domain: allegrolokalnie.9423021.sbs; TLS: connected=false)
malicious redirect
The .sbs TLD combined with a numeric SLD (9423021.sbs) is a known pattern used by phishing-as-a-service platforms that host multiple campaign subdomains (e.g., allegrolokalnie.9423021.sbs, inpost.9423021.sbs) under one numeric domain, often with redirect chains to credential harvesting pages. The failed TLS connection may indicate the redirect target is no longer active or has rotated. (location: domain: allegrolokalnie.9423021.sbs)
credential harvesting
Allegro Lokalnie impersonation sites are routinely used to harvest login credentials and payment information from Polish consumers. The brand-specific subdomain pattern targeting a marketplace platform is consistent with credential harvesting operations that present fake login or payment flows. (location: domain: allegrolokalnie.9423021.sbs)
curl https://api.brin.sh/domain/allegrolokalnie.9423021.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.9423021.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.