context safety score
A score of 70/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
hidden content
1 hidden or tiny iframe elements detected
malicious redirect
JavaScript on window.onload intercepts ALL anchor clicks and redirects the user to 'https://referencement.faciles.ovh/popunder/random_marketing.php' after opening the intended link in a new tab. This is a popunder/redirect hijack that fires once per hour per browser session via localStorage timestamp gating. Users clicking any link are silently redirected to an off-domain marketing URL. (location: page.html:35 — inline <script> in <header>)
hidden content
An iframe loads content from 'https://referencement.faciles.ovh/468.php?sma=598&bob=24716&bag=1&mba=6&cry=1417&eba=soniaban3&deta=4' with style 'background-color: blue; overflow:hidden; border:0px' and scrolling disabled. The iframe is inside a column with class 'd_none' (display:none), making it invisible to users. It silently loads third-party content with tracking parameters from the same off-domain operator behind the redirect script. (location: page.html:89 — <iframe> inside div.d_none)
social engineering
The site uses animated blinking CSS effects (classes 'clignote' and 'clignote1') on banner links to draw attention to affiliate traffic exchange sites, designed to encourage clicks to external referral URLs with affiliate/referral IDs embedded (e.g., ?rid=605, ?rid=374, ?ref=3). These are deceptive attention-manipulation techniques common in low-quality traffic exchange schemes. (location: page.html:210-226, 228-234 — inline <style> and affiliate banner links)
malicious redirect
The same off-domain operator (referencement.faciles.ovh / faciles.ovh) controls both the popunder redirect script and the hidden iframe, and is also linked in the footer as 'Top Click Exchange'. This establishes a coordinated traffic hijacking infrastructure where user clicks across the site are intercepted and routed through the operator's marketing pipeline. (location: page.html:290 — footer link to referencement.faciles.ovh/click_ex.php; page.html:35 and page.html:89 — script and iframe)
curl https://api.brin.sh/domain/click-exchange.ovhCommon questions teams ask before deciding whether to use this domain in agent workflows.
click-exchange.ovh currently scores 70/100 with a caution 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.