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.9384ue29472973472ueu28749234.bond' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds platform. The subdomain 'allegrolokalnie' directly mimics the brand name while using a randomly-generated, obfuscated second-level domain under the suspicious .bond TLD to evade detection. (location: domain: allegrolokalnie.9384ue29472973472ueu28749234.bond)
phishing
The domain structure — brand name as subdomain, randomized gibberish SLD, non-standard .bond TLD — is a classic phishing pattern used to deceive users and automated systems into believing the site is affiliated with the legitimate Allegro Lokalnie marketplace. TLS is not connected and certificate is invalid, consistent with a hastily-deployed phishing infrastructure. (location: url: https://allegrolokalnie.9384ue29472973472ueu28749234.bond)
credential harvesting
Brand impersonation of a marketplace platform (Allegro Lokalnie) combined with invalid TLS and obfuscated domain strongly indicates a credential harvesting operation targeting users' Allegro login credentials or payment information. The page content is empty, which may indicate the page was taken down, is geo-blocked, or serves content dynamically to targeted victims only. (location: domain: allegrolokalnie.9384ue29472973472ueu28749234.bond)
obfuscated code
The second-level domain '9384ue29472973472ueu28749234' is a randomly generated, high-entropy string consistent with domain generation algorithm (DGA) output or deliberate obfuscation to hinder blocklist detection and pattern-based filtering. (location: domain: 9384ue29472973472ueu28749234.bond)
curl https://api.brin.sh/domain/allegrolokalnie.9384ue29472973472ueu28749234.bondCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.9384ue29472973472ueu28749234.bond 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.