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.372736422.online' impersonates Allegro Lokalnie, a legitimate Polish e-commerce/classifieds platform (allegro.pl). The subdomain pattern 'allegrolokalnie' prepended to a numeric random domain '372736422.online' is a classic brand impersonation technique designed to deceive users into believing they are on the official Allegro Lokalnie site. (location: domain: allegrolokalnie.372736422.online)
phishing
The domain is structured as a phishing site targeting Allegro Lokalnie users. It uses the brand name as a subdomain on a disposable numeric .online TLD domain — a pattern strongly associated with credential-harvesting phishing campaigns against marketplace users in Poland and Eastern Europe. (location: domain: allegrolokalnie.372736422.online)
credential harvesting
Sites impersonating Allegro Lokalnie typically present fake login or payment pages to harvest user credentials or financial data. TLS connection failed (connected=false, cert_valid=false), suggesting the page may redirect or serve content via HTTP or an alternative channel, consistent with credential harvesting infrastructure. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
malicious redirect
TLS connection could not be established (connected=false, san_match=false, cert_valid=false). The site may be serving content over insecure channels or using redirects to external phishing or malware delivery pages. Numeric .online domains are frequently used as redirect hops in multi-stage phishing chains. (location: metadata.json: tls fields)
social engineering
The domain name 'allegrolokalnie.372736422.online' exploits user trust in the Allegro Lokalnie brand. Polish marketplace users are frequently targeted with fake parcel/payment notifications and buy-now scams. The convincing subdomain name is intended to lower victim suspicion and induce credential or payment submission. (location: domain: allegrolokalnie.372736422.online)
curl https://api.brin.sh/domain/allegrolokalnie.372736422.onlineCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.372736422.online 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.