context safety score
A score of 36/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.kr4tbkvksdcebrv.sbs' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds platform. The subdomain 'allegrolokalnie' directly mimics the brand name while hosted under a randomized, suspicious second-level domain 'kr4tbkvksdcebrv.sbs', a classic typosquatting/brand-hijacking pattern used to deceive users into believing they are visiting the legitimate Allegro Lokalnie site. (location: domain: allegrolokalnie.kr4tbkvksdcebrv.sbs)
phishing
The combination of brand impersonation via subdomain, use of a non-standard .sbs TLD, failed TLS connection (connected=false, cert_valid=false), and a randomly-generated-looking domain string are strong composite indicators of a phishing site designed to harvest credentials or payment data from users expecting the legitimate Allegro Lokalnie platform. (location: url: https://allegrolokalnie.kr4tbkvksdcebrv.sbs)
credential harvesting
Sites impersonating Allegro Lokalnie typically present fake login or payment forms to steal user credentials and financial data. The domain structure and TLS failure are consistent with credential harvesting infrastructure. No page content was retrievable, which may indicate active evasion, geo-blocking, or bot detection to hide the malicious payload from scanners. (location: domain: allegrolokalnie.kr4tbkvksdcebrv.sbs)
hidden content
The page returned empty HTML and text content despite the domain being reachable enough to be scanned. This is consistent with cloaking techniques where malicious content is served only to human victims (based on user-agent, IP geolocation, or referrer), while automated scanners receive a blank or minimal response to evade detection. (location: page.html, page-text.txt (both empty))
curl https://api.brin.sh/domain/allegrolokalnie.kr4tbkvksdcebrv.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.kr4tbkvksdcebrv.sbs currently scores 36/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.