Is salesforce-sites.com safe?

suspiciouslow confidence
40/100

context safety score

A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.

identity
100
behavior
80
content
0
graph
30

5 threat patterns detected

medium

encoded payload

suspicious base64-like blobs detected in page content

critical

brand impersonation

The domain salesforce-sites.com serves a complete pixel-perfect replica of the official Salesforce homepage (salesforce.com). The page uses Salesforce branding, logos, slogans ('The #1 AI CRM'), and content verbatim while the actual serving domain is not salesforce.com. The canonical tag and og:url both falsely claim the page is at https://www.salesforce.com/ to deceive users and crawlers. (location: domain: salesforce-sites.com; page.html line 5 (og:url), line 17 (canonical href), line 1 (title, favicon, meta content))

critical

phishing

The site impersonates Salesforce and presents a 'Start for free' CTA linking to a signup form (/form/signup/free-crm-v2/) and includes an embedded AI chat agent (Agentforce). Visitors who believe they are on salesforce.com may submit credentials, personal information, or corporate data to the attacker-controlled domain salesforce-sites.com. (location: page.html line 441-453 (free CRM signup CTA), line 44 (embedded agent config with org IDs and messaging URLs))

high

credential harvesting

The page embeds a live chat agent configuration (wpdata.agent) pointing to org62.my.salesforce-scrt.com and det.demo.my.salesforce-scrt.com with real Salesforce org IDs (00D000000000062, 00Dfh000001sFaz). An impersonating site hosting these forms and chat widgets could intercept user inputs including login credentials, business information, and personal data entered in chat or signup flows. (location: page.html line 44 (wpdata.agent JSON with orgId, messagingUrl, fallbackOrgId))

medium

malicious redirect

The og:url and canonical link both declare the page URL as https://www.salesforce.com/ while the actual serving domain is salesforce-sites.com. This misdirection can manipulate search engine indexing and social media link previews to appear as if content originates from the legitimate salesforce.com, redirecting trust to the impersonating domain. (location: page.html line 5 (og:url: https://www.salesforce.com/), line 10 (twitter:url), line 17 (canonical href: https://www.salesforce.com/))

API

curl https://api.brin.sh/domain/salesforce-sites.com

FAQ: how to interpret this assessment

Common questions teams ask before deciding whether to use this domain in agent workflows.

Is salesforce-sites.com safe for AI agents to use?

salesforce-sites.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.

How should I interpret the score and verdict?

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.

How does brin compute this domain score?

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.

What do identity, behavior, content, and graph mean for this domain?

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.

Why does brin scan packages, repos, skills, MCP servers, pages, and commits?

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.

Can I rely on a safe verdict as a full security guarantee?

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.

When should I re-check before using an entity?

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.

Last Scanned

March 4, 2026

Verdict Scale

safe80–100
caution50–79
suspicious20–49
dangerous0–19

Disclaimer

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.

start scoring agent dependencies.

integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.