context safety score
A score of 47/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
phishing
Domain dyndns.tv uses the well-known DynDNS brand name (a legitimate dynamic DNS service by Oracle) in a .tv TLD, suggesting potential brand impersonation or typosquatting to exploit user trust in the DynDNS name. (location: domain: dyndns.tv)
brand impersonation
The domain dyndns.tv mimics the legitimate DynDNS (dyn.com / dynudns.com) brand. DynDNS is a widely recognized DNS service; use of 'dyndns' in a .tv TLD is a classic brand-squatting pattern that could deceive users or automated agents into trusting the domain. (location: domain: dyndns.tv)
hidden content
TLS connection failed (connected=false, cert_valid=false) and page content is completely empty despite a reachable URL being submitted. This is consistent with cloaking behavior — serving empty or benign content to scanners while delivering malicious content to targeted browsers or user agents. (location: metadata.json: tls.connected=false; page.html and page-text.txt are empty)
social engineering
The combination of a brand-impersonating domain (dyndns.tv), failed TLS, and empty page content is a pattern associated with infrastructure used for phishing or social engineering campaigns that may be dormant or selectively activated. The domain name alone could be used in phishing emails or messages directing victims to what appears to be a trusted DNS service. (location: domain: dyndns.tv, metadata.json)
curl https://api.brin.sh/domain/dyndns.tvCommon questions teams ask before deciding whether to use this domain in agent workflows.
dyndns.tv currently scores 47/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.