context safety score
A score of 20/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
fresh domain risk
newly registered domain with privacy redaction and suspicious lexical profile
tls connection failed
Could not establish TLS connection
brand impersonation
The domain 'allegrolokalnie.76084.me' impersonates Allegro Lokalnie, a major Polish e-commerce/classifieds platform. The subdomain mimics the legitimate brand name 'allegrolokalnie' to deceive users into believing they are visiting an official Allegro service. (location: domain: allegrolokalnie.76084.me)
phishing
The domain combines brand impersonation of Allegro Lokalnie with a suspicious registrar-style numeric subdomain ('76084.me'), a pattern commonly used in phishing infrastructure to host fake login or payment pages targeting users of the impersonated platform. (location: domain: allegrolokalnie.76084.me)
credential harvesting
Domain impersonating Allegro Lokalnie (a platform requiring user login and payment details) on a 22-day-old domain with WHOIS privacy redacted and TLS not connected/invalid. This combination is consistent with credential harvesting infrastructure targeting Allegro users' login credentials and payment information. (location: domain: allegrolokalnie.76084.me)
social engineering
The domain is only 22 days old with WHOIS privacy redacted and unknown hosting reputation, while masquerading as a well-known brand. This is a hallmark of social engineering infrastructure designed to exploit user trust in the Allegro Lokalnie brand before the domain is detected and blocked. (location: metadata.json: domain_age_days=22, privacy_redacted=true, hosting.reputation=Unknown)
malicious redirect
TLS is not connected (connected=false, cert_valid=false) on a domain impersonating a trusted e-commerce brand. The page content was unretrievable, which may indicate the site redirects or gates access (e.g., geofencing, user-agent filtering) to evade automated scanners while serving malicious content to real victims. (location: metadata.json: tls.connected=false, tls.cert_valid=false; page.html and page-text.txt are empty)
curl https://api.brin.sh/domain/allegrolokalnie.76084.meCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.76084.me currently scores 20/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.