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.828928.sbs' directly impersonates Allegro Lokalnie, the Polish e-commerce/classifieds marketplace (allegro.pl/lokalnie). The subdomain 'allegrolokalnie' mimics the legitimate brand name while hosted under the suspicious registrable domain '828928.sbs', a classic brand-squatting pattern used in phishing and fraud campaigns targeting Polish users. (location: domain: allegrolokalnie.828928.sbs)
phishing
The domain construction — a well-known brand name ('allegrolokalnie') combined with a numeric, non-descriptive second-level domain ('828928') under a low-reputation TLD ('.sbs') — is a textbook phishing domain pattern. TLS connection failed (connected=false, cert_valid=false), meaning the site either is down, blocking automated scanners, or evading detection while remaining accessible to targeted victims via direct links. (location: metadata.json: tls.connected=false, tls.cert_valid=false, domain=allegrolokalnie.828928.sbs)
social engineering
The .sbs TLD combined with a numeric SLD and a brand-impersonating subdomain is a pattern frequently used in social engineering campaigns, particularly those distributed via SMS (smishing) or messaging apps targeting marketplace users. Victims are lured to fake listing or payment pages mimicking Allegro Lokalnie to steal credentials or payment data. (location: domain: allegrolokalnie.828928.sbs)
credential harvesting
Allegro Lokalnie impersonation sites are well-documented vectors for harvesting login credentials and payment card data from Polish consumers. The failed TLS and empty page content is consistent with a site that serves content only to targeted traffic (e.g., via direct link), hiding from crawlers and scanners while presenting a fake login or payment page to victims. (location: domain: allegrolokalnie.828928.sbs; page.html and page-text.txt are empty, suggesting cloaking or traffic-gated content delivery)
curl https://api.brin.sh/domain/allegrolokalnie.828928.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.828928.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.