context safety score
A score of 42/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 'ultradns2.com' impersonates the legitimate UltraDNS DNS service (ultradns.com) by appending '2' to the brand name. This is a classic typosquatting/brand impersonation pattern targeting users or automated systems seeking UltraDNS services. (location: domain: ultradns2.com)
phishing
The domain closely mimics the legitimate UltraDNS brand (ultradns.com) and fails TLS validation (connected=false, cert_valid=false), which is consistent with a phishing or deceptive site infrastructure that has not properly provisioned SSL. Legitimate DNS infrastructure providers maintain valid TLS certificates. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
A domain impersonating a DNS/network infrastructure provider (UltraDNS) with no valid TLS and empty page content is a common setup for credential harvesting campaigns targeting IT administrators or automated provisioning agents that may attempt to authenticate against what they believe is the real UltraDNS portal. (location: domain: ultradns2.com, metadata.json)
malicious redirect
The page returned empty HTML and text content despite the domain being active and registered for nearly 4 years (1426 days). This blank-page pattern is commonly used in redirect chains, where the real payload is served conditionally (e.g., based on user-agent, referrer, or geolocation), concealing malicious redirects from scanners. (location: page.html (empty), page-text.txt (empty))
hidden content
All content files (page.html, page-text.txt, page-hidden.txt) are empty despite the domain being long-lived and active. This anomaly suggests content may be hidden behind bot-detection or served only to targeted victims, which is a known evasion technique. (location: page.html, page-text.txt, page-hidden.txt (all empty))
curl https://api.brin.sh/domain/ultradns2.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
ultradns2.com currently scores 42/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.