context safety score
A score of 32/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.5hgdscjj3jbvjsd.sbs' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds platform. The subdomain 'allegrolokalnie' directly mimics the brand name while hosted under a randomized, suspicious second-level domain ('5hgdscjj3jbvjsd.sbs'), a classic typosquatting/subdomain spoofing technique used to deceive users into believing they are on a legitimate Allegro property. (location: domain: allegrolokalnie.5hgdscjj3jbvjsd.sbs)
phishing
The combination of a brand-impersonating subdomain (allegrolokalnie), a randomly-generated suspicious parent domain (5hgdscjj3jbvjsd.sbs), a non-functional TLS connection (connected=false, cert_valid=false), and an empty page body is consistent with a phishing infrastructure page — either a parked lure, a redirect gateway, or a page that only renders content to targeted victims. The .sbs TLD is commonly associated with phishing campaigns. (location: domain: allegrolokalnie.5hgdscjj3jbvjsd.sbs; TLS block in metadata.json)
malicious redirect
The page returned empty HTML and text content despite a reachable URL structure. This is a strong indicator of a conditional redirect setup where the server serves content only to specific user agents, geolocations, or referrer sources — a technique used to evade automated scanners while redirecting human victims to credential harvesting or phishing pages. (location: page.html (empty); page-text.txt (empty))
credential harvesting
The domain impersonates Allegro Lokalnie, a platform where users exchange goods and payments. Impersonation of such a platform is a well-known vector for harvesting login credentials, payment details, and personal data. The infrastructure pattern (random domain, brand subdomain, invalid TLS, empty page to scanners) is consistent with credential harvesting operations targeting Polish users. (location: domain: allegrolokalnie.5hgdscjj3jbvjsd.sbs)
curl https://api.brin.sh/domain/allegrolokalnie.5hgdscjj3jbvjsd.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.5hgdscjj3jbvjsd.sbs currently scores 32/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.