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.5o5bovcxmw3.sbs' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds marketplace. The subdomain string 'allegrolokalnie' is a direct copy of the legitimate brand name 'Allegro Lokalnie' (lokalnie.allegro.pl), hosted under a suspicious randomly-generated second-level domain '5o5bovcxmw3.sbs' with a low-reputation .sbs TLD, a classic typosquatting/brand-impersonation pattern. (location: domain: allegrolokalnie.5o5bovcxmw3.sbs)
phishing
The domain structure — legitimate brand name ('allegrolokalnie') prepended to a random-looking domain under a non-standard TLD (.sbs) — is a well-established phishing pattern used to deceive users into believing they are visiting the real Allegro Lokalnie platform. TLS is not connected and cert is invalid, meaning the site cannot establish a trusted secure connection, consistent with a hastily-deployed phishing site. (location: domain: allegrolokalnie.5o5bovcxmw3.sbs; TLS: connected=false, cert_valid=false)
credential harvesting
Brand impersonation of a major marketplace (Allegro Lokalnie) combined with an invalid TLS certificate and empty page content strongly suggests a credential harvesting operation. The site likely presents a fake login or payment form to capture user credentials or financial data, consistent with Polish marketplace phishing campaigns frequently targeting Allegro users. (location: domain: allegrolokalnie.5o5bovcxmw3.sbs; metadata.json TLS fields)
malicious redirect
The page content is entirely empty (page.html, page-text.txt, page-hidden.txt all contain no content) despite the domain being resolvable. This is consistent with a redirect-only phishing landing page that serves content dynamically or conditionally (e.g., only to targeted traffic, specific geolocations, or referral sources), hiding its malicious payload from automated scanners. (location: page.html (empty); page-text.txt (empty); page-hidden.txt (empty))
curl https://api.brin.sh/domain/allegrolokalnie.5o5bovcxmw3.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.5o5bovcxmw3.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.