context safety score
A score of 39/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 'otrqdrscbe.xyz' uses a randomly-generated, nonsensical string as a name — a strong indicator of a throwaway phishing or malware-distribution domain. The .xyz TLD is frequently abused for low-cost disposable phishing infrastructure. (location: metadata.json: domain)
phishing
TLS connection failed entirely (connected=false, cert_valid=false). The site cannot establish a valid HTTPS session, which means either the server is intentionally down between campaigns, the infrastructure is being cycled, or the domain is parked awaiting payload deployment. Legitimate sites do not present with completely broken TLS. (location: metadata.json: tls)
hidden content
Page HTML, visible text, and hidden text are all empty despite the domain resolving through hosting infrastructure. This blank-page pattern is consistent with a cloaked or gated phishing page that only serves content to targeted victims (e.g., via referrer check, geofencing, or user-agent filtering), hiding malicious content from scanners. (location: page.html, page-text.txt, page-hidden.txt)
malicious redirect
A live domain with hosting ('MajorCloud') that returns no content is a common staging pattern for redirect chains: the domain acts as a hop point that serves a redirect only to qualifying traffic, evading static analysis while routing victims to a downstream payload or credential-harvesting page. (location: metadata.json: hosting, page.html (empty))
social engineering
WHOIS domain age is null/unknown and privacy status is unresolved, indicating either very recent registration or deliberate opacity. Newly registered domains with opaque ownership are a primary vector for social-engineering campaigns where trust has not yet been established and blocklists have not yet flagged the domain. (location: metadata.json: whois)
curl https://api.brin.sh/domain/otrqdrscbe.xyzCommon questions teams ask before deciding whether to use this domain in agent workflows.
otrqdrscbe.xyz currently scores 39/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.