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.42387421.sbs' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds platform (allegro.pl). The subdomain string 'allegrolokalnie' mimics the legitimate brand name to deceive users into trusting the site, while the actual registrable domain '42387421.sbs' is a randomly-numbered throwaway domain under the suspicious .sbs TLD commonly used in fraud campaigns. (location: domain: allegrolokalnie.42387421.sbs)
phishing
The combination of brand impersonation targeting a major e-commerce platform (Allegro), a non-standard numeric throwaway domain (42387421.sbs), failed TLS connection (connected=false, cert_valid=false), and empty page content is consistent with a phishing infrastructure page — either a parked lure awaiting deployment, a page that requires specific referrer/user-agent conditions to serve malicious content, or one whose content was not captured due to TLS failure. (location: url: https://allegrolokalnie.42387421.sbs)
malicious redirect
The page returned empty content despite a reachable URL structure, which is a common indicator of conditional redirection — serving benign or empty content to scanners/bots while redirecting targeted victims (e.g., based on geolocation, referrer, or user-agent) to a phishing or credential-harvesting page. The .sbs TLD and numeric domain pattern are frequently observed in redirect chain infrastructure. (location: url: https://allegrolokalnie.42387421.sbs)
credential harvesting
Allegro Lokalnie impersonation sites are a well-documented phishing vector in Poland and Central Europe, typically designed to harvest payment credentials, login credentials, or personal identification under the guise of completing a classifieds transaction. The domain pattern matches known Allegro credential-harvesting campaigns. (location: domain: allegrolokalnie.42387421.sbs)
curl https://api.brin.sh/domain/allegrolokalnie.42387421.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.42387421.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.