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.349110.cyou' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds platform. The subdomain 'allegrolokalnie' directly copies the brand name while using a suspicious numeric registrar-style second-level domain '349110.cyou' under the .cyou TLD, a classic typosquatting/brand-abuse pattern used for fraud and phishing targeting Allegro users. (location: domain: allegrolokalnie.349110.cyou)
phishing
The combination of a brand-impersonating domain (allegrolokalnie.349110.cyou) with a failed TLS connection (connected=false, cert_valid=false) is strongly indicative of a phishing site. Legitimate Allegro Lokalnie services operate on official domains with valid TLS. This infrastructure pattern is consistent with credential harvesting or payment fraud pages targeting Allegro users. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
Domain impersonating Allegro Lokalnie (a marketplace requiring user login and payment details) with invalid TLS on a .cyou TLD is a high-confidence credential harvesting setup. Users deceived into visiting this site may submit their Allegro login credentials or payment card data to attacker-controlled infrastructure. (location: domain: allegrolokalnie.349110.cyou)
malicious redirect
The page returned empty HTML and text content despite the domain being live enough to have metadata collected. This is consistent with a redirect-based attack, cloaking, or a page that serves malicious content conditionally (e.g., only to mobile users, specific geolocations, or referrers from SMS/email phishing links), evading static analysis. (location: page.html: empty, page-text.txt: empty)
hidden content
All content files (page.html, page-text.txt, page-hidden.txt) are empty, yet the domain resolves and metadata was collected. This cloaking behavior — serving blank or benign content to crawlers while delivering malicious content to real victims — is a known evasion technique used by phishing kits to avoid detection and blocklisting. (location: page.html, page-text.txt, page-hidden.txt: all empty)
curl https://api.brin.sh/domain/allegrolokalnie.349110.cyouCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.349110.cyou 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.