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.88518.cfd' directly impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds platform (allegro.pl / allegrolokalnie.pl). The subdomain prefix 'allegrolokalnie' mimics the legitimate brand while using a suspicious registrar numeric subdomain under a non-standard TLD (.cfd), a classic typosquatting/brand-impersonation pattern used in phishing campaigns targeting Polish consumers. (location: domain: allegrolokalnie.88518.cfd)
phishing
The domain structure (brand name + numeric subdomain + .cfd TLD) is a well-documented phishing pattern. TLS connection failed entirely (connected=false, cert_valid=false), meaning the site either serves content over HTTP or has a broken/invalid certificate — highly atypical for a legitimate commerce site and consistent with a hastily-deployed phishing page. The .cfd TLD is widely abused in phishing infrastructure. (location: metadata.json: tls.connected=false, tls.cert_valid=false, domain: allegrolokalnie.88518.cfd)
credential harvesting
Impersonation of Allegro Lokalnie combined with a failed TLS configuration strongly indicates a credential harvesting setup. Victims searching for or redirected to this domain would likely be presented with a fake Allegro login page designed to steal account credentials and/or payment information. The empty page content suggests the page may gate content behind interaction (e.g., only renders after JS execution or form submission). (location: domain: allegrolokalnie.88518.cfd, metadata.json)
malicious redirect
The numeric subdomain pattern '88518.cfd' is consistent with bulletproof hosting or redirect infrastructure used in phishing kits, where a numeric domain acts as a staging/redirect layer routing victims through multiple hops before landing on the actual harvesting page. The empty HTML and text content at crawl time supports this — the page may redirect or require specific conditions to render. (location: domain: allegrolokalnie.88518.cfd, page.html (empty))
social engineering
Impersonating a trusted local marketplace (Allegro Lokalnie) targets users who expect to buy/sell goods locally. This brand trust exploitation is a social engineering vector: victims believe they are on a legitimate platform and willingly enter credentials, personal data, or complete fake payment flows. (location: domain: allegrolokalnie.88518.cfd)
curl https://api.brin.sh/domain/allegrolokalnie.88518.cfdCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.88518.cfd 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.