context safety score
A score of 44/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
Domain 'splunkdns.net' incorporates the trademarked 'Splunk' brand (Cisco/Splunk enterprise security software) combined with 'dns', a common technique to impersonate a legitimate vendor's infrastructure or tooling to deceive users or automated agents into trusting the domain. (location: domain: splunkdns.net)
phishing
The domain impersonates Splunk (a major enterprise security platform) and has no valid TLS certificate and returns no page content, consistent with a staged phishing domain that may serve targeted content to specific victims while appearing empty to scanners. (location: domain: splunkdns.net, TLS: connected=false, cert_valid=false)
malicious redirect
The site returns no content to the crawler but has an active domain registration. This is consistent with a domain used for redirect chains or conditional redirection (e.g., serving redirects only to certain user-agents, IPs, or referrers) to evade automated analysis. (location: page.html: empty, page-text.txt: empty)
hidden content
All page content files are empty (page.html, page-text.txt, page-hidden.txt), yet the domain is actively registered and resolves. Content may be hidden behind user-agent filtering, IP geofencing, or JavaScript rendering, preventing static analysis from detecting the actual payload. (location: page.html: empty, page-text.txt: empty, page-hidden.txt: empty)
social engineering
The domain name 'splunkdns.net' is constructed to appear as an official Splunk DNS service or infrastructure endpoint, which could deceive IT/security professionals or AI agents into treating it as a legitimate Splunk-related resource. (location: domain: splunkdns.net)
curl https://api.brin.sh/domain/splunkdns.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
splunkdns.net currently scores 44/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.