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
Domain my-salesforce-hub.com serves a full clone of the official Salesforce homepage, including Salesforce logos, trademarks, navigation, content, and structured data. The page falsely claims to be salesforce.com in og:url, canonical link, and JSON-LD Organization schema, constituting direct brand impersonation of Salesforce. (location: page.html:1-5, og:url meta tag; page.html:17, canonical href; page.html:18, JSON-LD @type:Organization with url:https://www.salesforce.com/)
phishing
The cloned Salesforce page on the non-Salesforce domain my-salesforce-hub.com presents sign-up and free CRM calls-to-action that direct users to Salesforce credential/account creation flows. A user or AI agent deceived by the brand impersonation could submit credentials or personal data believing they are on the legitimate salesforce.com. (location: page.html:441-453, CTA href https://www.salesforce.com/form/signup/free-crm-v2/?d=pb; page.html:508-521, Start demo CTA)
social engineering
The page impersonates Salesforce's official homepage with full branding, customer testimonials (PepsiCo, Volkswagen, Heathrow, FedEx, OpenTable, reMarkable), and authoritative statistics (3M+ conversations, 66% autonomous case resolution) to build false trust and legitimacy on a domain not affiliated with Salesforce. (location: page.html:625-830 (customer story blades), page-text.txt:543-551)
hidden content
The og:url canonical tag and JSON-LD structured data actively misrepresent the true hosting domain to web crawlers, AI agents, and search engines by asserting the page identity as https://www.salesforce.com/ while actually served from my-salesforce-hub.com. This metadata deception hides the true origin. (location: page.html:5, og:url=https://www.salesforce.com/; page.html:10, twitter:url=https://www.salesforce.com/; page.html:17, canonical=https://www.salesforce.com/; page.html:18, JSON-LD url field)
prompt injection
The page is a full Salesforce clone served from a lookalike domain. An AI agent browsing or indexing this page would receive structured data, canonical tags, and og:url all asserting identity as salesforce.com, potentially causing the agent to treat this malicious domain as the authoritative Salesforce source and act on it accordingly (e.g., following its links, trusting its content, submitting data). (location: page.html:17-18, canonical and JSON-LD identity assertions pointing to salesforce.com from my-salesforce-hub.com)
curl https://api.brin.sh/domain/my-salesforce-hub.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
my-salesforce-hub.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.