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.5287542566754.sbs' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds marketplace. The subdomain string directly incorporates the brand name 'allegrolokalnie' while using a suspicious numeric second-level domain under the '.sbs' TLD, a classic typosquatting/brand-hijacking pattern used to deceive users into believing they are on the legitimate Allegro platform. (location: domain: allegrolokalnie.5287542566754.sbs)
phishing
The domain construction — brand name as subdomain + random numeric SLD + uncommon TLD (.sbs) — is a hallmark phishing infrastructure pattern. The site failed TLS connection entirely (connected=false, cert_valid=false), indicating either a misconfigured or intentionally stripped HTTPS setup commonly seen in phishing pages that rotate infrastructure rapidly. Combined with brand impersonation of a major Polish marketplace, this is consistent with a phishing campaign targeting Allegro Lokalnie users. (location: domain: allegrolokalnie.5287542566754.sbs; TLS: connected=false)
credential harvesting
Allegro Lokalnie impersonation sites are routinely used for credential harvesting — tricking users into entering login credentials believing they are on the legitimate platform. The infrastructure characteristics (brand-name subdomain, numeric SLD, .sbs TLD, failed TLS) match known credential-harvesting phishing kits targeting Polish e-commerce users. Page content could not be retrieved, which may indicate the page is gated, geo-restricted, or serves different content to automated scanners. (location: domain: allegrolokalnie.5287542566754.sbs)
social engineering
The use of 'allegrolokalnie' as the subdomain prefix is a deliberate social engineering tactic to establish false legitimacy. Users seeing this URL may believe it is a legitimate subdomain or regional variant of the Allegro Lokalnie service. The .sbs TLD (commonly associated with low-cost domain registrations used in scam infrastructure) and numeric SLD further obscure the fraudulent nature of the domain from non-technical users. (location: domain: allegrolokalnie.5287542566754.sbs)
curl https://api.brin.sh/domain/allegrolokalnie.5287542566754.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.5287542566754.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.