context safety score
A score of 32/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.ko3f3p.sbs' impersonates Allegro Lokalnie, a well-known Polish e-commerce/classifieds platform. The subdomain 'allegrolokalnie' is prepended to a randomly-generated, low-reputation .sbs TLD domain 'ko3f3p.sbs', a classic brand impersonation pattern used to deceive users into believing they are on the legitimate allegrolokalnie.pl site. (location: domain: allegrolokalnie.ko3f3p.sbs)
phishing
The combination of brand impersonation of Allegro Lokalnie with a suspicious registrar domain (ko3f3p.sbs), failed TLS connection, and unknown hosting reputation strongly indicates a phishing site targeting users of the legitimate Allegro Lokalnie marketplace. The site likely harvests credentials or payment information from Polish e-commerce users. (location: url: https://allegrolokalnie.ko3f3p.sbs)
credential harvesting
Allegro Lokalnie impersonation sites are a known attack vector in Poland for harvesting login credentials and payment card data. The domain structure follows documented phishing kit patterns that mimic the Allegro Lokalnie login and transaction flows to steal user credentials and financial information. (location: domain: allegrolokalnie.ko3f3p.sbs)
malicious redirect
The TLS connection failure (connected=false, cert_valid=false) combined with a non-blocklisted but suspicious domain suggests the site may be used as an intermediate redirect node in a phishing chain, or may redirect users to credential-harvesting pages after an initial landing. The .sbs TLD and randomized second-level domain (ko3f3p) are consistent with infrastructure used for redirect chains. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
curl https://api.brin.sh/domain/allegrolokalnie.ko3f3p.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.ko3f3p.sbs currently scores 32/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.