context safety score
A score of 34/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.75845.cfd' impersonates Allegro Lokalnie, a major Polish online marketplace (allegro.pl / allegrolokalnie.pl). The use of a lookalike subdomain-style prefix with a suspicious .cfd TLD is a classic brand impersonation technique designed to deceive users into believing they are visiting the legitimate Allegro Lokalnie platform. (location: domain: allegrolokalnie.75845.cfd)
phishing
The domain mimics a trusted e-commerce brand (Allegro Lokalnie) using a fraudulent TLD (.cfd — commonly associated with scam/phishing infrastructure). TLS connection failed entirely (connected=false, cert_valid=false), indicating the site either is non-functional, behind a gateway that strips TLS, or was taken down after deployment — all consistent with phishing site lifecycle patterns. (location: domain: allegrolokalnie.75845.cfd, TLS metadata)
credential harvesting
Domains impersonating Allegro Lokalnie are routinely used to harvest login credentials, payment card data, and personal information from Polish users expecting to interact with the legitimate marketplace. The combination of brand impersonation and a throwaway .cfd TLD strongly indicates credential harvesting intent, even though the page content could not be retrieved. (location: domain: allegrolokalnie.75845.cfd)
malicious redirect
The .cfd TLD and numeric subdomain pattern (75845.cfd) is consistent with bulletproof hosting or redirect infrastructure used to chain victims through intermediate domains before landing on phishing pages. The TLS failure may indicate the page has already rotated or the domain serves as a redirect node. (location: domain: allegrolokalnie.75845.cfd, hosting: Unknown)
curl https://api.brin.sh/domain/allegrolokalnie.75845.cfdCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.75845.cfd currently scores 34/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.