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.4245264.sbs' impersonates Allegro Lokalnie, a major Polish online marketplace. It combines the legitimate brand name 'allegrolokalnie' with a suspicious numeric subdomain pattern under the '.sbs' TLD, a common technique used to create convincing fake sites while evading exact-match detection. (location: domain: allegrolokalnie.4245264.sbs)
phishing
The domain structure (brand name + numeric ID + uncommon TLD '.sbs') is a hallmark of phishing infrastructure. The TLS certificate is invalid and the connection failed (connected=false, cert_valid=false), indicating a likely credential-harvesting or redirect phishing page that may not be fully operational or is gated/conditional. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
Combining the Allegro Lokalnie brand impersonation with a non-standard numeric domain pattern strongly suggests this site is designed to harvest credentials (login, payment details) from users expecting to interact with the legitimate Allegro Lokalnie platform. (location: domain: allegrolokalnie.4245264.sbs)
malicious redirect
The numeric subdomain pattern (4245264.sbs) is characteristic of bulletproof hosting or redirect infrastructure used to chain victims through intermediate domains. The empty page content despite a live URL suggests the page may serve as a redirect node that delivers content conditionally based on referrer, user-agent, or geolocation. (location: metadata.json: hosting.reputation=Unknown; page.html and page-text.txt are empty)
curl https://api.brin.sh/domain/allegrolokalnie.4245264.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.4245264.sbs 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.