context safety score
A score of 36/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
obfuscated code
Two identical large obfuscated JavaScript blocks appear in the page (lines 32 and 763 of page.html). Each uses URL-encoded strings, a character-rotation cipher (Caesar-style with position-based shifting mod 95), and string-index slicing to reconstruct URLs and logic at runtime. The payload is not human-readable and conceals what third-party endpoints are contacted, what fingerprinting is performed, and what ad/tracking scripts are loaded. The pattern is consistent with ad-fraud or malvertising loaders. (location: page.html:32 and page.html:763 (inline <script data-cfasync="false"> blocks))
malicious redirect
An external script is loaded from //clammyendearedkeg.com/bn.js — a domain with no recognizable legitimate owner, using a nonsense name pattern common in malvertising networks. The script is loaded asynchronously with data-cfasync="false" (bypassing Cloudflare scanning) and fires a callback function kpqesxet(16) on both load and error, suggesting it is part of the obfuscated ad-injector network reconstructed by the obfuscated inline script. (location: page.html:33 (<script src="//clammyendearedkeg.com/bn.js">))
malicious redirect
An external script is loaded from //bodybossmotivate.com/on.js — another suspiciously named domain with no recognizable affiliation, loaded with data-cfasync="false" and callbacks fzfrsxso(15) on load and error. This mirrors the pattern of the clammyendearedkeg.com loader and is consistent with a secondary malvertising or redirect-chain script injected by the obfuscated bootstrap code. (location: page.html:764 (<script src="//bodybossmotivate.com/on.js">))
brand impersonation
The site's meta keywords and description explicitly claim to be archives of TikTok, Instagram, Facebook, OnlyFans, Chaturbate, Stripchat, Camsoda, and other platforms. The site name 'Archivebate' is a deliberate blend of 'Chaturbate' and 'archive', trading on Chaturbate's brand recognition. Platform names are used as primary SEO keywords to attract users searching for those legitimate platforms. (location: page.html:10-12 (meta keywords and description tags))
social engineering
A full-screen age-verification overlay (z-index: 99999999999999) with a single 'Continue' button is shown on page load. This dark-pattern gate provides no real age verification — it is a one-click bypass designed to create a false sense of compliance (showing RTA and 18+ logos) while conditioning users to click through prompts, a technique used to normalise consent-clicking that can be repurposed for downstream social engineering (e.g., push notification permission grabs or redirects). (location: page.html:37-83 (<section id="verification">))
hidden content
Three sets of ad-slot placeholder divs (data-cl-spot attributes with IDs 1959498, 1956918, 1956917, and three instances of 2010741) contain no visible content in the static HTML but are populated dynamically by the obfuscated loader scripts. The actual ad content served into these slots is fully opaque and could include malvertising, phishing lures, or further redirect chains not visible in the static page source. (location: page.html:265-273 and page.html:769-777 (data-cl-spot divs))
obfuscated code
The Cloudflare email-protection encoding at /cdn-cgi/l/email-protection#70030500... encodes an email address in the contact modal footer link. While Cloudflare's bot-protection encoding is a known technique, it makes the destination address opaque to automated scanners and to users, potentially obscuring a spoofed or malicious email address used in the DMCA/contact flow. (location: page.html:851 (<a href="/cdn-cgi/l/email-protection#70030500...">Proceed to email</a>))
curl https://api.brin.sh/domain/archivebate.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
archivebate.com currently scores 36/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.