context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
brand impersonation
The domain salesforceliveagent.com is serving an exact replica of the official Salesforce homepage (salesforce.com), including Salesforce logos, branding, Schema.org Organization structured data with Salesforce's corporate address, and all product content. This is a lookalike domain impersonating Salesforce to deceive users and AI agents. (location: metadata.json (domain: salesforceliveagent.com), page.html lines 1-18)
phishing
The page is a full clone of salesforce.com served from the non-Salesforce domain salesforceliveagent.com. The canonical URL, og:url, and twitter:url all declare the page as 'https://www.salesforce.com/' while it is actually served from salesforceliveagent.com, a classic phishing technique to spoof legitimacy while intercepting traffic intended for Salesforce. (location: page.html lines 5, 10, 17 (canonical, og:url, twitter:url all point to www.salesforce.com))
malicious redirect
All canonical and Open Graph metadata declares the origin as https://www.salesforce.com/ while the actual serving domain is salesforceliveagent.com. This domain-mismatch pattern is used to mislead AI agents and crawlers into attributing the content to the legitimate salesforce.com domain. (location: page.html line 5 (og:url), line 10 (twitter:url), line 17 (canonical href))
social engineering
The page uses official Salesforce trust signals — including Schema.org verified organization data, OV TLS certificate, DigiCert issuer, Salesforce corporate address (415 Mission Street, San Francisco), and phone number 1-800-664-9073 — to create a false sense of legitimacy from a non-Salesforce domain. This is designed to manipulate AI agents into trusting the site as an authoritative Salesforce source. (location: page.html line 18 (application/ld+json structured data), metadata.json (TLS cert_type: Ov))
curl https://api.brin.sh/domain/salesforceliveagent.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
salesforceliveagent.com currently scores 40/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.