context safety score
A score of 43/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
cloaking
Page loads content in transparent or zero-size iframe overlay
brand impersonation
The domain cloudfilter.net is serving content that fully impersonates Cloudmark (a Proofpoint brand). The page presents itself as the official Cloudmark website, using Proofpoint/Cloudmark branding, logos, favicons, navigation, and product listings. The canonical URL and og:url both point to www.cloudmark.com, while the actual serving domain is cloudfilter.net — a different, unrelated domain masquerading as the legitimate Cloudmark site. (location: page.html lines 16-17, 40-44; metadata.json domain field)
malicious redirect
The page sets canonical and og:url tags to https://www.cloudmark.com/en while being served from cloudfilter.net. This is a domain misdirection pattern: users visiting cloudfilter.net are presented with content designed to appear as if they are on the legitimate cloudmark.com domain, while actually remaining on the attacker-controlled cloudfilter.net domain. (location: page.html lines 16-17, 42)
hidden content
A Pardot marketing tracker script is injected inside a div with class 'element-invisible' and inline style 'clear:both', effectively hiding it from visual rendering. The script dynamically loads https://pi.pardot.com/pd.js and sets account IDs (piAId='149101', piCId='1093'), enabling covert visitor tracking without user awareness. (location: page.html lines 1050-1063)
hidden content
Multiple inline <style> blocks are rendered as visible text content in page-text.txt (lines 99-539), indicating CSS was injected into content areas rather than proper style tags. This causes raw CSS rules to be exposed in the text layer, which could be used to confuse text-based parsers or AI agents processing the page content. (location: page-text.txt lines 99-539)
curl https://api.brin.sh/domain/cloudfilter.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
cloudfilter.net currently scores 43/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.