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.30019.click' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds platform (allegrolokalnie.pl). The subdomain mimics the legitimate brand name while using a suspicious '.click' TLD under the '30019.click' registrar domain, a classic typosquatting/brand-abuse pattern used to deceive users into believing they are on the official site. (location: domain: allegrolokalnie.30019.click)
phishing
The domain construction — combining a well-known brand name ('allegrolokalnie') with a low-reputation numeric '.click' parent domain ('30019.click') — is a textbook phishing infrastructure pattern. TLS connection failed (connected=false, cert_valid=false), meaning the site either serves no valid HTTPS or uses an invalid certificate, consistent with a hastily-assembled phishing page. (location: metadata.json: tls.connected=false, tls.cert_valid=false, domain=allegrolokalnie.30019.click)
credential harvesting
Allegro Lokalnie impersonation sites are commonly used to harvest login credentials, payment details, or personal information from Polish users expecting to interact with the legitimate classifieds marketplace. The brand impersonation combined with failed TLS is consistent with credential-harvesting infrastructure. (location: domain: allegrolokalnie.30019.click)
malicious redirect
The '.click' TLD combined with a numeric second-level domain ('30019.click') acting as a parent for subdomains is a known pattern for redirect/traffic distribution systems (TDS) used in malware and phishing campaigns. The site may serve as a redirect node routing victims to downstream phishing or malware pages. (location: domain: allegrolokalnie.30019.click (TLD: .click, parent: 30019.click))
curl https://api.brin.sh/domain/allegrolokalnie.30019.clickCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.30019.click 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.