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
brand impersonation
The domain canekilttantrum.com hosts a page that fully impersonates Clickadu s.r.o.'s official privacy policy, using Clickadu's branding, logo (embedded as a base64 SVG), company name, address, Tax ID, and linking to clickadu.com. The domain has no affiliation with Clickadu and presents itself as an authoritative Clickadu property to deceive visitors. (location: page.html:4, page.html:5, page.html:153-155, page.html:159, page.html:299-301)
social engineering
The page poses as a legitimate privacy policy and 'Subscription Management Guide' for a push notification ad network. It provides step-by-step instructions guiding users to interact with browser notification settings, which is a common tactic used by malicious ad networks to manage or retain push notification subscriptions obtained through deceptive means. The page exists to legitimize unwanted push notification subscriptions. (location: page.html:181-253, page-text.txt:31-103)
credential harvesting
The page contains an 'Unsubscribe' button that silently POSTs a JSON payload (including a timestamp) to the /unsubscribe endpoint on canekilttantrum.com via XHR. This interaction can be used to confirm active browser sessions, validate that a push subscription token is live, and harvest subscriber identifiers server-side without user awareness of what data is transmitted. (location: page.html:272-277, page.html:323-365)
hidden content
The logo image is a large base64-encoded SVG embedded inline (data:image/svg+xml;base64,...) rather than a hosted image file. This technique obscures the actual image content from cursory inspection and can be used to hide steganographic payloads or avoid URL-based image scanning. The encoded content is too large to decode inline and warrants further inspection. (location: page.html:154)
hidden content
The 'Subscription Management Guide' section is collapsed by default (CSS class 'collapse:not(.show) { display: none }') and only revealed on user click. This hides instructional content from casual page review and automated scanners that do not simulate user interaction, reducing visibility of the push-notification manipulation instructions. (location: page.html:87-89, page.html:186)
curl https://api.brin.sh/domain/canekilttantrum.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
canekilttantrum.com 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.