context safety score
A score of 49/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 itvarnigtr.xyz uses a randomized, non-descriptive string pattern typical of auto-generated phishing or malware campaign domains. The TLS connection failed entirely (connected=false, cert_valid=false), meaning the site cannot establish a trusted HTTPS session, which is a strong indicator of a malicious or abandoned infrastructure asset. (location: metadata.json: domain, tls fields)
malicious redirect
The page returned completely empty HTML and no visible text content despite the domain being reachable enough to have metadata collected. Empty page bodies are a common pattern for cloaked redirect pages that serve different content based on user-agent, referrer, or geolocation — delivering benign empty responses to scanners while redirecting real users to malicious payloads. (location: page.html, page-text.txt: empty content)
hidden content
The .brin-context.md references a page-hidden.txt file for extracted hidden content, but the file is empty. Combined with the empty page.html, this is consistent with a cloaking strategy where hidden or injected content is only rendered in live browser sessions with JavaScript execution, evading static analysis. (location: page-hidden.txt: empty; page.html: empty)
brand impersonation
The domain itvarnigtr.xyz has no resolvable TLS certificate (issuer=null, cert_type=Unknown) and a fully opaque identity (WHOIS privacy_redacted status unknown). The hosting is on MajorCloud infrastructure. This combination — random-looking domain, no valid TLS, anonymous registration — is consistent with infrastructure set up to impersonate a legitimate brand without leaving traceable ownership. (location: metadata.json: tls.issuer, whois.privacy_redacted)
curl https://api.brin.sh/domain/itvarnigtr.xyzCommon questions teams ask before deciding whether to use this domain in agent workflows.
itvarnigtr.xyz currently scores 49/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.