context safety score
A score of 34/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
prompt injection
Hidden HTML element contains AI-targeting instructions
malicious redirect
The scanned URL is cldin.eu but the page content, canonical URL, og:url, and all branding/links point exclusively to www.yourhosting.nl. The domain cldin.eu is silently serving the full Yourhosting.nl website, indicating an undisclosed redirect or domain alias that masks the true origin from users and automated agents. (location: metadata.json: url=https://cldin.eu; page.html line 17: canonical href=https://www.yourhosting.nl/; page.html line 22: og:url=https://www.yourhosting.nl/)
brand impersonation
The domain cldin.eu presents itself entirely as Yourhosting.nl — including its logo, branding, product pages, login links, and all internal navigation — without any disclosure that the visitor is on cldin.eu rather than yourhosting.nl. This constitutes brand impersonation of the legitimate Dutch hosting provider Yourhosting. (location: page.html lines 13, 98, 1124: title and logo branded as 'Yourhosting'; page.html line 6: favicon loaded from www.yourhosting.nl)
credential harvesting
The page presents login links ('Mijn Yourhosting' and 'Webmail') pointing to login.account.yourhosting.nl and webmail.yourhosting.nl. Users landing on cldin.eu who believe they are on the legitimate Yourhosting site may be induced to click these login links, potentially harvesting credentials if the redirect chain is altered or if users are confused about the true domain. (location: page.html lines 152-153: login links to login.account.yourhosting.nl and webmail.yourhosting.nl served under cldin.eu domain)
hidden content
Multiple navigation menu items use inline style 'font-size: 0' which renders their text invisible to users but visible to screen readers and automated agents/crawlers. While this is a common accessibility anti-pattern, the pervasive use across all footer and header nav links could also obscure link destinations from human visitors. (location: page.html lines 132, 138-160, 1142-1194: style='font-size: 0;' applied to numerous anchor elements throughout header and footer navigation)
hidden content
The OpenAI npm package (openai@5.8.2) is loaded as a deferred script directly in the page, and the basel JS config exposes an 'openai_key' field (currently empty string). Loading the OpenAI client-side library on a public-facing page is unusual and could be used to relay user input to an AI backend in ways not disclosed to the visitor. (location: page.html line 1263: src='.../npm/openai@5.8.2/index.min.js'; page.html line 1271: var basel = {...,"openai_key":"",...))
curl https://api.brin.sh/domain/cldin.euCommon questions teams ask before deciding whether to use this domain in agent workflows.
cldin.eu currently scores 34/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.