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
The domain 'adobepass.com' impersonates Adobe by incorporating the Adobe brand name into the domain. The legitimate Adobe authentication/pass service is operated by Adobe Inc. at official Adobe domains. This domain is not affiliated with Adobe and uses the brand to mislead users or downstream systems. (location: domain: adobepass.com)
phishing
The domain 'adobepass.com' combines a well-known brand (Adobe) with the word 'pass', a common phishing pattern used to harvest credentials or authentication tokens by impersonating a login/SSO portal. Despite domain age of ~13.7 years, the site returned no content (empty page.html and page-text.txt), which may indicate the site is dormant, cloaking content, or selectively serving payloads. (location: domain: adobepass.com)
credential harvesting
The combination of 'adobe' + 'pass' in the domain strongly suggests intent to harvest Adobe account credentials or authentication pass tokens. TLS is not connected and certificate is invalid (tls.connected=false, cert_valid=false), meaning any credentials submitted would also be transmitted insecurely. (location: domain: adobepass.com, metadata.json tls block)
malicious redirect
The site returned completely empty HTML content despite being reachable enough to have metadata collected. This blank-page behavior is consistent with a redirect-only site that conditionally routes victims to malicious destinations based on user-agent, referrer, or other fingerprinting — a technique used to evade automated scanners. (location: page.html (empty), page-text.txt (empty))
hidden content
The page returned no visible text and no HTML content, yet the domain resolves and metadata was collected. Empty or near-empty pages that are live can indicate cloaked or hidden content served only to targeted victims, bots instructed by the site operator, or JavaScript-rendered payloads not captured in static analysis. (location: page.html (empty), page-hidden.txt (empty), page-text.txt (empty))
curl https://api.brin.sh/domain/adobepass.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
adobepass.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.