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.734942.top' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds platform. The subdomain 'allegrolokalnie' is a direct name-clone of the legitimate brand hosted under a suspicious numeric registrar-style TLD '734942.top', a classic typosquatting/brand-hijacking pattern used to deceive users into believing they are on the official Allegro Lokalnie site. (location: domain: allegrolokalnie.734942.top)
phishing
The site combines brand impersonation of a trusted Polish marketplace (Allegro Lokalnie) with a failed/invalid TLS connection (connected=false, cert_valid=false), indicating the site may be a phishing landing page designed to harvest credentials or payment data from users who believe they are on the legitimate platform. The absence of valid HTTPS is a strong phishing signal. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
malicious redirect
The domain uses a .top TLD under a numeric second-level domain (734942.top), a pattern commonly associated with bulk-registered redirect and phishing infrastructure. The page content is empty, suggesting the site may serve as a redirect hop or that content is dynamically loaded to evade static scanners. (location: domain: allegrolokalnie.734942.top, page.html: empty)
credential harvesting
Impersonation of Allegro Lokalnie — a platform where users log in and conduct financial transactions — combined with invalid TLS and empty static page content strongly suggests a credential harvesting operation. Users tricked into visiting may be prompted to enter login credentials or payment details on a fraudulent form loaded dynamically. (location: domain: allegrolokalnie.734942.top, metadata.json)
curl https://api.brin.sh/domain/allegrolokalnie.734942.topCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.734942.top 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.