context safety score
A score of 49/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 'alipaydns.com' impersonates Alipay, a major financial payments brand owned by Ant Group/Alibaba. The name combines 'alipay' (a well-known payment platform) with 'dns', a common technique to appear infrastructure-related while trading on brand recognition. This pattern is commonly used for phishing, credential harvesting, or malicious DNS redirection targeting Alipay users or systems. (location: domain: alipaydns.com)
phishing
The domain closely mimics the legitimate Alipay brand (alipay.com) by appending 'dns' as a subdomain-style suffix in the apex domain. This typosquatting/combosquatting pattern is a well-established phishing vector used to deceive users or automated agents into trusting the domain as an official Alipay service. (location: domain: alipaydns.com)
malicious redirect
TLS connection failed entirely (connected=false, cert_valid=false) for alipaydns.com. The site is unreachable over HTTPS, which may indicate the domain is parked, used for DNS-layer redirection, or configured to redirect traffic at the network/DNS level rather than serving content directly — consistent with DNS hijacking or traffic interception infrastructure. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
Combination of brand impersonation of a major payment platform (Alipay) with a failed TLS connection and empty page content is consistent with a domain held in reserve or rotating for credential harvesting campaigns. The domain age of 5455 days (~14.9 years) suggests long-term holding, possibly for reputation laundering or intermittent phishing campaign use. (location: domain: alipaydns.com, metadata.json: whois.domain_age_days=5455)
curl https://api.brin.sh/domain/alipaydns.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
alipaydns.com currently scores 49/100 with a suspicious 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.