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.78884g9g9.bond' impersonates Allegro Lokalnie, a legitimate Polish e-commerce/classifieds platform (allegrolokalnie.pl). The subdomain prefix mimics the brand name exactly while the actual domain '78884g9g9.bond' is a randomly-generated throwaway domain under a low-trust TLD (.bond), a classic brand impersonation pattern used in phishing campaigns targeting Polish users. (location: domain: allegrolokalnie.78884g9g9.bond)
phishing
The combination of a brand-impersonating subdomain (allegrolokalnie), a randomized parent domain (78884g9g9.bond), failed TLS connection (connected=false, cert_valid=false), and no blocklist hit strongly indicates a newly stood-up phishing site. The .bond TLD is heavily abused for short-lived phishing infrastructure. The page returned no content, consistent with a site that is either gating content behind redirects, user-agent checks, or geographic filtering to evade crawlers while serving malicious content to real victims. (location: domain: allegrolokalnie.78884g9g9.bond, TLS: connected=false)
malicious redirect
The page returned empty HTML and empty visible text despite the domain being live enough to have a known URL. This is consistent with server-side cloaking or redirect chains that serve content only to targeted victims (e.g., based on user-agent, referrer, geolocation, or device type), a common technique to evade automated scanners while redirecting real users to credential-harvesting pages. (location: page.html (empty), page-text.txt (empty))
credential harvesting
Allegro Lokalnie impersonation sites are routinely used to harvest login credentials and payment card data by presenting fake login or transaction confirmation pages. The infrastructure pattern (random .bond domain, TLS failure, brand-name subdomain) matches known Allegro phishing kits documented in Polish cybersecurity incident reports. Even though page content was not retrieved, the domain pattern alone is a strong indicator of credential harvesting intent. (location: domain: allegrolokalnie.78884g9g9.bond)
curl https://api.brin.sh/domain/allegrolokalnie.78884g9g9.bondCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.78884g9g9.bond 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.