context safety score
A score of 69/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
malicious redirect
The page immediately redirects all visitors via JavaScript (window.location.href) to 'https://www.company.enelxway.com/en'. The destination domain 'company.enelxway.com' is a subdomain that differs from the canonical domain 'www.enelxway.com' referenced in meta tags and hreflang links. This pattern — serving content from enelxway.it but redirecting to a 'company.' subdomain — is inconsistent with legitimate brand infrastructure and may route users to a controlled third-party or attacker-owned host. (location: page.html:20 — window.location.href = "https:\/\/www.company.enelxway.com\/en")
brand impersonation
The site presents itself as 'Enel X Way' (a real EV charging brand by Enel Group) using official branding assets, favicon paths, and AEM (Adobe Experience Manager) CMS infrastructure cloned from the legitimate enelxway.com. However, it is served from 'enelxway.it' rather than the legitimate 'enelxway.com', and immediately redirects to 'company.enelxway.com' — a subdomain not consistent with Enel's official web presence. The combination of a lookalike domain (.it vs .com) with cloned CMS structure is a strong brand impersonation signal. (location: page.html:4 (title: Enel X Way), line 32 (canonical: enelxway.com), line 20 (redirect to company.enelxway.com))
social engineering
The page is a near-empty shell with no real visible content (page-text.txt is almost entirely whitespace and script output), yet it loads extensive third-party tracking and analytics (Adobe DTM/Launch, Microsoft Clarity, YouTube iframe API, WordLift). Combined with the immediate redirect, this pattern is consistent with a watering-hole or pass-through page designed to silently profile and redirect visitors rather than serve legitimate content. (location: page.html:79 (Adobe DTM), page.html:82 (YouTube iframe API), page.html:103 (WordLift), page.html:509-515 (Microsoft Clarity tag m87c5am9fs))
curl https://api.brin.sh/domain/enelxway.itCommon questions teams ask before deciding whether to use this domain in agent workflows.
enelxway.it currently scores 69/100 with a caution verdict and medium 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.