context safety score
A score of 36/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
The Auth0 redirectUri is set to 'https://armani-main.netlify.app/api/auth0/authorize' — a third-party Netlify staging domain rather than an official armani.com endpoint. OAuth authorization codes and tokens could be redirected to and captured by this non-official domain if it is not controlled by Armani. (location: page.html:182 / page-text.txt:2 — window.__NUXT__.config.public.auth0.redirectUri)
credential harvesting
Auth0 client credentials (clientID: XWuJ7o1iiYLE0gK0zCm4Pgd6sxUsKoE9, domain: auth.armani.com) are exposed in the public JavaScript config bundle. Combined with the Netlify redirect URI, this could facilitate token theft or account takeover against users authenticating via this flow. (location: page.html:182 — window.__NUXT__.config.public.auth0)
malicious redirect
A preconnect link to 'https://8eurk2.us' is present in the HTML head. This is an opaque, randomly-named .us domain with no obvious relationship to Armani or any known legitimate CDN/analytics vendor. Establishing a preconnect to an unrecognized domain may indicate a supply-chain injection, data exfiltration endpoint, or malicious redirect infrastructure. (location: page.html:6 — <link rel="preconnect" href="https://8eurk2.us">)
hidden content
The page exposes multiple sensitive API keys and tokens in the public JavaScript config, including a Google Maps API key, Algolia search API key, PayPal client ID, reCAPTCHA site key, and Datadog client token. While some exposure is normal for client-side SDKs, aggregating all these keys in a single public payload increases the attack surface for abuse. (location: page.html:182 — window.__NUXT__.config.public (google, algolia.apiKey, paypal.clientId, recaptcha.key, datadog.ddClientToken))
curl https://api.brin.sh/domain/armani.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
armani.com currently scores 36/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.