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.ltrbkvkcmebrvcdsr.sbs' impersonates 'Allegro Lokalnie', the Polish e-commerce marketplace (allegro.pl). The subdomain/prefix 'allegrolokalnie' directly copies the brand name to deceive users into believing they are visiting a legitimate Allegro Lokalnie page. (location: domain: allegrolokalnie.ltrbkvkcmebrvcdsr.sbs)
phishing
The domain structure combines a well-known brand name ('allegrolokalnie') with a randomly-generated-looking second-level domain ('ltrbkvkcmebrvcdsr') under the suspicious TLD '.sbs'. This pattern is characteristic of phishing infrastructure designed to harvest credentials or payment data from users who trust the Allegro brand. (location: domain: allegrolokalnie.ltrbkvkcmebrvcdsr.sbs)
credential harvesting
TLS connection failed (connected=false, cert_valid=false), meaning the site either does not serve HTTPS properly or is currently down/rotating infrastructure. Combined with brand impersonation of a major e-commerce platform, this strongly suggests a credential harvesting operation targeting Allegro Lokalnie users, potentially collecting login credentials or payment details. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
hidden content
The context file references a 'page-hidden.txt' for extracted hidden content, and all content files (page.html, page-text.txt, page-hidden.txt) are empty. This may indicate the page employs cloaking techniques — serving empty or benign content to crawlers/scanners while delivering malicious content to targeted human visitors based on referrer, user-agent, or geolocation. (location: page.html, page-text.txt, page-hidden.txt (all empty))
malicious redirect
The randomized SLD 'ltrbkvkcmebrvcdsr' is consistent with algorithmically-generated domain names used in redirect chains and fast-flux phishing networks. The empty page content combined with a live domain registration suggests the site may function as a redirect hop rather than a terminal phishing page, routing victims through disposable domains. (location: domain: ltrbkvkcmebrvcdsr.sbs)
curl https://api.brin.sh/domain/allegrolokalnie.ltrbkvkcmebrvcdsr.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.ltrbkvkcmebrvcdsr.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.