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
Domain 'allegrolokalnie.dla-ciebie-oferty16253.sbs' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds marketplace. The subdomain prefix 'allegrolokalnie' directly mimics the brand name to deceive users into believing they are on the legitimate Allegro Lokalnie platform. (location: domain: allegrolokalnie.dla-ciebie-oferty16253.sbs)
phishing
The domain construction follows a classic phishing pattern: brand name ('allegrolokalnie') combined with a lure phrase ('dla-ciebie-oferty' = 'for-you-offers' in Polish) on a suspicious .sbs TLD. This is consistent with phishing pages targeting Polish Allegro Lokalnie users, typically harvesting login credentials or payment data. (location: domain: allegrolokalnie.dla-ciebie-oferty16253.sbs)
credential harvesting
The combination of brand impersonation of a marketplace platform, lure phrase suggesting personalized offers ('dla-ciebie-oferty'), and numeric identifier ('16253') is a known pattern for credential harvesting campaigns targeting Polish e-commerce users. TLS connection failed (connected=false, cert_valid=false), indicating the site may be down or evading crawlers while still being distributed via phishing links. (location: domain: allegrolokalnie.dla-ciebie-oferty16253.sbs; tls.connected=false)
social engineering
The path segment 'dla-ciebie-oferty' translates to 'offers for you' in Polish, a social engineering lure designed to create a sense of personalization and urgency to entice targets to visit and interact with the fraudulent page. (location: domain subdomain path: dla-ciebie-oferty16253.sbs)
malicious redirect
The .sbs TLD combined with a numeric suffix ('16253') and TLS failure suggests this may be one of many auto-generated phishing domains in a campaign, potentially acting as a redirect gateway or short-lived landing page routing victims to a payload or credential harvesting site. The page content returned empty, consistent with conditional serving or bot-detection evasion. (location: domain: allegrolokalnie.dla-ciebie-oferty16253.sbs; page.html empty; tls.connected=false)
curl https://api.brin.sh/domain/allegrolokalnie.dla-ciebie-oferty16253.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.dla-ciebie-oferty16253.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.