context safety score
A score of 37/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
social engineering
Domain 'wareztv.io' is a warez/piracy-themed site — a classic social engineering vector used to lure users seeking free/pirated content, commonly used to distribute malware, force ad interactions, or harvest credentials under the pretense of free media access. (location: domain: wareztv.io)
malicious redirect
TLS connection failed (connected=false, cert_valid=false) on a site hosted on bulletproof infrastructure. The site may be non-responsive to legitimate scanners while actively serving content to targeted users, potentially through redirects or cloaking techniques. (location: metadata.json: tls.connected=false, hosting.reputation=Bulletproof)
hidden content
The page.html, page-text.txt, and page-hidden.txt files are all empty despite the domain being active and hosted on bulletproof infrastructure. This is consistent with cloaking — serving empty/benign content to scanners/bots while delivering malicious content to real users based on User-Agent, IP geolocation, or referrer checks. (location: page.html, page-text.txt, page-hidden.txt (all empty))
phishing
Bulletproof hosting is strongly associated with phishing operations. The domain's warez branding combined with bulletproof infrastructure and TLS failure is a pattern consistent with phishing pages that abuse content piracy themes to harvest credentials or payment data. (location: metadata.json: hosting.reputation=Bulletproof)
brand impersonation
The name 'wareztv' mimics legitimate streaming services (TV streaming platforms). Warez-themed domains frequently impersonate brands like Netflix, Hulu, or Twitch to deceive users into submitting credentials or payment information. (location: domain: wareztv.io)
curl https://api.brin.sh/domain/wareztv.ioCommon questions teams ask before deciding whether to use this domain in agent workflows.
wareztv.io currently scores 37/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.