context safety score
A score of 36/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
encoded payload
suspicious base64-like blobs detected in page content
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The domain aboutcookies.org presents itself as a neutral informational resource ('About Cookies') but is actually operated by Pinsent Masons LLP, a commercial law firm. The site title, meta tags, og:site_name, and page heading all use 'About Cookies' with no immediate disclosure of the commercial operator, while all branding assets, logos, copyright, and legal links resolve to pinsentmasons.com. This creates a deceptive appearance of an independent public-interest resource to harvest user trust and cookie consent interactions. (location: page.html:<title>, meta name='application-name', og:site_name, footer copyright line 494)
brand impersonation
The JSON-LD structured data block declares the organization name as 'About Cookies' with legalName 'Pinsent Masons LLP' and includes a suspicious sameAs Twitter handle 'https://twitter.com/linked-aboutcookiesKhoa' that appears to be a user-generated or test account handle mixed with a legitimate handle '@about-cookies', suggesting possible manipulation of the organization's social identity graph. (location: page.html:line 72, script type='application/ld+json')
social engineering
The site is operated by a law firm (Pinsent Masons LLP) but presents as an independent educational cookie information site. Visitors are prompted to accept cookies via a consent banner without being informed they are interacting with a law firm's data collection infrastructure. The consent UI ('Your privacy matters to us') uses trust-building language while the actual data controller identity is obscured. (location: page.html:lines 508-526, cookie consent banner)
hidden content
HTML comments embed legacy IE conditional blocks (IE 6 through IE 9) that inject different html class attributes. While this is a historic compatibility pattern, it can be abused to serve alternate content to specific user agents. The page also contains inline style blocks and a meta release/build tag ('#{Octopus.Release.Package}/0.0.160') that leaks internal CI/CD pipeline variable syntax, indicating a template placeholder was not substituted, which could expose deployment infrastructure details to fingerprinting. (location: page.html:lines 2-8 (IE conditionals), line 14 (build meta tag))
curl https://api.brin.sh/domain/aboutcookies.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
aboutcookies.org currently scores 36/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.