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.728264.sbs' impersonates Allegro Lokalnie, a major Polish online marketplace. The subdomain mimics the legitimate brand name 'allegrolokalnie' (allegrolokalnie.pl) while using a suspicious numeric registrar-style TLD '728264.sbs', a classic typosquatting/brand-impersonation pattern used to deceive users into believing they are on the official Allegro Lokalnie platform. (location: domain: allegrolokalnie.728264.sbs)
phishing
The domain structure — brand name + numeric second-level domain + .sbs TLD — is a well-known phishing infrastructure pattern. The .sbs TLD combined with a numeric SLD (728264) is commonly used by phishing kit operators to host credential-harvesting pages under convincing subdomains. TLS connection failed (connected=false, cert_valid=false), indicating the site may be down, recently stood up, or deliberately avoiding certificate transparency logging. (location: domain: allegrolokalnie.728264.sbs, metadata.json: tls.connected=false)
credential harvesting
The combination of brand impersonation of a marketplace platform (Allegro Lokalnie) with a suspicious infrastructure domain strongly suggests the site is designed to harvest login credentials and/or payment information from users who believe they are logging into the legitimate Allegro Lokalnie service. (location: domain: allegrolokalnie.728264.sbs)
malicious redirect
The use of a numeric SLD (728264.sbs) as the parent domain with a brand-name subdomain is consistent with redirect infrastructure where the numeric domain serves as a hub routing victims across multiple phishing subdomains. The failed TLS connection may indicate the redirect chain was active at time of submission but the final payload host is intermittent or rate-limited. (location: domain: allegrolokalnie.728264.sbs, metadata.json: tls fields)
curl https://api.brin.sh/domain/allegrolokalnie.728264.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.728264.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.