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
Domain 'allegrolokalnie.gsfs-gtnygds-asfde4.top' impersonates Allegro Lokalnie, a major Polish e-commerce marketplace, by prepending 'allegrolokalnie' as a subdomain prefix on a randomly-generated, clearly fraudulent domain (gsfs-gtnygds-asfde4.top). This is a classic brand spoofing pattern designed to deceive users into believing they are visiting the legitimate Allegro platform. (location: domain: allegrolokalnie.gsfs-gtnygds-asfde4.top)
phishing
The domain structure — a well-known brand name prefixed to a randomized gibberish domain — is a hallmark of phishing infrastructure. The TLS connection failed (connected=false, cert_valid=false), meaning the site either serves content over HTTP or has a broken/expired certificate, consistent with hastily-deployed phishing pages. The combination of brand impersonation + invalid TLS + random domain strongly indicates an active phishing campaign targeting Allegro Lokalnie users. (location: domain: allegrolokalnie.gsfs-gtnygds-asfde4.top, TLS: connected=false, cert_valid=false)
credential harvesting
Sites impersonating Allegro Lokalnie typically present fake login pages to harvest user credentials (email, password) and/or payment card details. The domain pattern is consistent with known credential-harvesting phishing kits targeting Polish e-commerce users. (location: domain: allegrolokalnie.gsfs-gtnygds-asfde4.top)
social engineering
The use of the legitimate brand name 'allegrolokalnie' at the start of the subdomain is a deliberate social engineering tactic to reduce user suspicion and increase click-through and form submission rates. Users scanning a URL quickly may see 'allegrolokalnie' and assume legitimacy without inspecting the full domain. (location: domain: allegrolokalnie.gsfs-gtnygds-asfde4.top)
curl https://api.brin.sh/domain/allegrolokalnie.gsfs-gtnygds-asfde4.topCommon questions teams ask before deciding whether to use this domain in agent workflows.
allegrolokalnie.gsfs-gtnygds-asfde4.top 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.