context safety score
A score of 46/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page uses meta refresh redirect
malicious redirect
Page immediately redirects all visitors via JavaScript (window.location.replace) to a tracking URL with a unique UUID and browser fingerprint parameter. The redirect fires within 300ms via setTimeout as a fallback, ensuring no visitor escapes tracking regardless of fingerprint success. (location: page.html:6-15, script block)
hidden content
An anchor tag '<a href=...>Click here to enter</a>' is wrapped in a div with 'display: none', hiding it from human users while remaining accessible to crawlers and AI agents. The hidden link contains the same tracking UUID and a distinct fingerprint value (fp=-3), suggesting it is planted specifically to be followed by non-browser agents. (location: page.html:32)
prompt injection
The hidden anchor element with visible text 'Click here to enter' is concealed from human view but exposed in extracted page text (page-text.txt:2). This is a classic prompt injection vector: an AI agent parsing page text would see an instruction ('Click here to enter') and may follow the link, triggering the tracking/redirect pipeline without user awareness. (location: page.html:32, page-text.txt:2)
social engineering
The noscript meta-refresh tag silently redirects users who have JavaScript disabled to the same tracking URL (fp=-5), ensuring universal redirection. Combined with the hidden link and JS redirect, the page uses multi-vector coercion to guarantee all visitor types — human, bot, and AI agent — are funneled through a fingerprinting and tracking pipeline. (location: page.html:33)
obfuscated code
The page loads an external obfuscated fingerprinting library from '/js/fingerprint/iife.min.js' (FingerprintJS) and uses it to silently collect a unique visitor identifier before redirecting. The fingerprint value is appended to the redirect URL, enabling persistent cross-session tracking of visitors without consent or disclosure. (location: page.html:4, script block lines 18-23)
curl https://api.brin.sh/domain/coppersurfer.tkCommon questions teams ask before deciding whether to use this domain in agent workflows.
coppersurfer.tk currently scores 46/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.