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
brand impersonation
Domain 'adobecqms.net' impersonates Adobe by incorporating the 'adobe' brand name in a non-Adobe registered domain. The 'cqms' suffix is characteristic of typosquatting or brand-abuse domains used to deceive users into believing the site is affiliated with Adobe Inc. (location: metadata.json: domain field, .brin-context.md: URL/Domain)
phishing
The domain 'adobecqms.net' combines a major brand name (Adobe) with an opaque suffix and fails TLS validation (connected=false, cert_valid=false). This pattern — brand name + meaningless suffix + no valid TLS — is a strong indicator of a phishing infrastructure site, likely used to harvest Adobe credentials or redirect victims. (location: metadata.json: tls block, .brin-context.md: TLS fields)
credential harvesting
Adobe-impersonating domains with invalid or absent TLS are routinely deployed for credential harvesting campaigns targeting Adobe Creative Cloud, Adobe Sign, and Adobe ID users. The absence of any resolvable page content (empty page.html, page-text.txt, page-hidden.txt) is consistent with a parked or intermittently-active phishing page that serves login forms only under specific traffic conditions. (location: metadata.json: tls.connected=false, tls.cert_valid=false; page.html: empty; page-text.txt: empty)
malicious redirect
The site returned no page content despite being reachable at the domain level, which is consistent with server-side conditional redirects that serve benign or empty content to crawlers/scanners while redirecting targeted victims (e.g., by referrer, user-agent, or geolocation) to a malicious payload or phishing page. (location: page.html: empty; page-text.txt: empty; metadata.json: blocklist.listed=false)
curl https://api.brin.sh/domain/adobecqms.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
adobecqms.net 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.