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.dla-ciebie-oferty15253.sbs' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds platform. The subdomain prefix 'allegrolokalnie' mimics the legitimate brand name while the actual registered domain is 'dla-ciebie-oferty15253.sbs' — a classic subdomain spoofing / brand impersonation pattern designed to deceive users into believing the site is affiliated with the official Allegro Lokalnie service. (location: domain: allegrolokalnie.dla-ciebie-oferty15253.sbs)
phishing
The domain construction — brand name as subdomain combined with a generic Polish phrase 'dla-ciebie-oferty' (meaning 'offers for you') and a random numeric suffix on a low-reputation .sbs TLD — is a hallmark phishing pattern used to harvest credentials or payment data from users who believe they are interacting with the legitimate Allegro Lokalnie platform. (location: domain: allegrolokalnie.dla-ciebie-oferty15253.sbs)
credential harvesting
TLS connection failed (connected=false, cert_valid=false), meaning the site either serves over HTTP or has an invalid certificate. Combined with the brand impersonation pattern, this is consistent with a credential harvesting page that collects login or payment credentials under a trusted brand facade, potentially without even enforcing encrypted transport. (location: metadata.json: tls fields (connected=false, cert_valid=false, san_match=false))
social engineering
The phrase 'dla-ciebie-oferty' ('offers for you') embedded in the domain name is a social engineering lure designed to create urgency or enticement, enticing users to click and interact with a fraudulent site posing as a legitimate marketplace offer. Numeric suffix '15253' suggests mass-generated phishing infrastructure. (location: domain: dla-ciebie-oferty15253.sbs)
curl https://api.brin.sh/domain/allegrolokalnie.dla-ciebie-oferty15253.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.dla-ciebie-oferty15253.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.