context safety score
A score of 46/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 'volcengine-dns.com' impersonates Volcengine, the cloud platform operated by ByteDance. It mimics the legitimate brand name 'volcengine' (volcengine.com) while appending '-dns' to appear as an official DNS or infrastructure service. This is a classic combosquatting pattern used to deceive users and automated agents into trusting the domain as an official Volcengine service. (location: domain: volcengine-dns.com)
phishing
The domain closely mimics a legitimate major cloud provider (Volcengine/ByteDance) with a subdomain-style suffix '-dns', a common phishing tactic to impersonate DNS or infrastructure services. The TLS certificate is invalid and the site failed to establish a secure connection (connected=false, cert_valid=false), which is consistent with a phishing or parked malicious domain that may not yet be fully deployed or is being used for non-HTTPS credential harvesting. (location: domain: volcengine-dns.com, TLS status: connected=false, cert_valid=false)
malicious redirect
The domain is registered, has been active for over 1200 days, and serves no visible content (empty page.html, page-text.txt, page-hidden.txt). A long-lived domain with no public content is consistent with a domain held in reserve for future malicious redirection campaigns, or currently acting as a silent redirect/landing stub that only activates under specific conditions (e.g., specific user agents, referrers, or geographic targets). (location: domain: volcengine-dns.com, page.html: empty, page-text.txt: empty)
social engineering
The combination of a recognized brand name ('volcengine') with a technical-sounding suffix ('-dns') is a social engineering tactic designed to instill false trust in both human users and AI agents processing URLs. DNS-related domains are frequently used to deceive users into modifying network settings, installing software, or submitting credentials under the pretense of a legitimate service operation. (location: domain: volcengine-dns.com)
curl https://api.brin.sh/domain/volcengine-dns.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
volcengine-dns.com currently scores 46/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.