context safety score
A score of 49/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
malicious redirect
script/meta redirect patterns detected in page source
brand impersonation
Domain eugdpr.org impersonates the EU GDPR regulatory brand. The official EU GDPR information is not hosted at a .org domain by this name; this domain mimics the authoritative GDPR source to deceive users and agents into trusting its content as official EU regulatory guidance. (location: domain: eugdpr.org)
malicious redirect
The Cloudflare challenge page embeds cZone='minervapatterns.com', meaning the actual backend zone/origin is minervapatterns.com — a completely unrelated domain to eugdpr.org. The visitor is being silently proxied through or associated with a different domain, constituting domain fronting or a covert redirect to a mismatched backend. (location: page.html: <script> window._cf_chl_opt cZone='minervapatterns.com')
hidden content
The page sets meta robots to 'noindex,nofollow', actively suppressing search engine indexing and link-following. Combined with a Cloudflare interstitial that hides the true content behind a JavaScript challenge, the actual page content is concealed from crawlers and security scanners. (location: page.html: <meta name='robots' content='noindex,nofollow'>)
social engineering
The site presents itself as an EU GDPR authority domain (eugdpr.org) while serving only a Cloudflare challenge interstitial. This pattern is consistent with a site that shows different content to real users versus automated scanners, a cloaking technique used to serve malicious or deceptive content selectively. (location: page.html: full page / page-text.txt)
curl https://api.brin.sh/domain/eugdpr.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
eugdpr.org currently scores 49/100 with a suspicious verdict and medium 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.