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 salesforce-setup.com is serving a full clone of the official Salesforce homepage (www.salesforce.com), replicating branding, logos, product names, trademarks, customer testimonials, and navigation. The canonical and og:url tags explicitly claim to be www.salesforce.com while the actual serving domain is salesforce-setup.com. (location: page.html:1,5,10,17 — <title>, og:url, twitter:url, link rel=canonical)
phishing
The site impersonates Salesforce on a lookalike domain (salesforce-setup.com) with a pixel-perfect clone of the official homepage. CTAs such as 'Start for free' link to www.salesforce.com signup forms, but the deceptive domain and clone structure are consistent with a phishing operation designed to harvest user trust, credentials, or session tokens. (location: page.html:441,453 — href=https://www.salesforce.com/form/signup/free-crm-v2/)
credential harvesting
The page embeds a live Agentforce chat interface (af-v3-userinput-and-prompts) connected to org62.my.salesforce-scrt.com, which could be used to collect user inputs, personal information, or credentials entered into the chat widget under the false belief the user is on the official Salesforce site. (location: page.html:44,126 — wpdata.agent messagingUrl, <af-v3-userinput-and-prompts>)
social engineering
The page uses high-trust social proof elements (PepsiCo, Volkswagen, FedEx, Heathrow, OpenTable, reMarkable executive testimonials and logos) copied from the official Salesforce site to build false legitimacy and lower user suspicion on the impersonator domain. (location: page.html:932,1159,1393,1627 — eyebrow logo images and executive quote sections)
hidden content
The <meta property='visitor' content='prospect'> tag silently segments all visitors as sales prospects, indicating visitor profiling/tracking behavior embedded in the page metadata. (location: page.html:1 — <meta property='visitor' content='prospect'>)
curl https://api.brin.sh/domain/salesforce-setup.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
salesforce-setup.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.