context safety score
A score of 40/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 'gandi-ns.fr' impersonates Gandi, a legitimate and well-known domain registrar and hosting provider (gandi.net). The '-ns' suffix and '.fr' TLD are classic typosquatting/brand-impersonation tactics designed to deceive users or automated agents into trusting the domain as an official Gandi nameserver or service endpoint. (location: domain: gandi-ns.fr)
phishing
The domain closely mimics Gandi's brand ('gandi-ns.fr' vs 'gandi.net') and TLS is not connected/valid, which is consistent with a phishing or credential-harvesting infrastructure site that may serve deceptive login pages or redirect flows. The absence of valid TLS on a domain impersonating a registrar is a strong phishing indicator. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
Combination of brand impersonation of a domain registrar (Gandi) with no valid TLS and no resolvable/renderable page content suggests the site may be used to harvest registrar credentials (domain login, payment info) from users or AI agents that trust the Gandi brand. Registrar credential theft enables domain hijacking. (location: domain: gandi-ns.fr, metadata.json: tls fields)
malicious redirect
The site returned no HTML or text content despite being reachable enough to be scanned. This blank/empty response pattern is consistent with a redirect-only infrastructure node, cloaking behavior, or a conditional redirect that serves malicious content only to specific user-agents or geographic regions while appearing empty to scanners. (location: page.html (empty), page-text.txt (empty))
hidden content
All content files (page.html, page-text.txt, page-hidden.txt) are completely empty despite the domain being active and scanned. This may indicate cloaking: the server detects automated/scanning user-agents and withholds content, serving malicious payloads only to targeted victims such as real browsers or specific AI agent user-agent strings. (location: page.html (0 bytes), page-text.txt (0 bytes), page-hidden.txt (0 bytes))
curl https://api.brin.sh/domain/gandi-ns.frCommon questions teams ask before deciding whether to use this domain in agent workflows.
gandi-ns.fr currently scores 40/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.