context safety score
A score of 41/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
cloaking
Page conditionally redirects based on referrer or user-agent
cloaking
Page loads content in transparent or zero-size iframe overlay
malicious redirect
Three external JavaScript files loaded from adxsrver.com (note typo vs legitimate 'adxserver') with cf-async=false forcing synchronous execution: KstJsPp.js, license.11.js, kstst.js. This domain is a known ad/redirect network used on adult sites to deliver pop-unders and interstitials. (location: page.html:141-143)
malicious redirect
JavaScript interstitial redirect system (kstSettings) configured to inject a full-page interstitial sourced from track.gpsecureads.com for Chrome users, and a pop-under from flowdow.com for other browsers. The interstitial URL is https://track.gpsecureads.com/ac2e6380-efb5-4263-b9b2-de0024da5ab4?var1=advfapintersoda. This system fires on DOMContentLoaded, redirecting users before they can interact with the page. (location: page.html:161-207)
malicious redirect
An ad unit is embedded as a native feed post disguised as legitimate content (class 'feedorig'), using an iframe sourced from track.gpsecureads.com and presenting itself as 'Camsoda' with a user avatar and follow-style UI. The tracking domain gpsecureads.com is used across multiple ad redirect links on the page. This deceptive native ad placement is designed to blend into the content feed. (location: page.html:971-1011)
social engineering
Multiple 'Follow Free' and 'See all content' calls-to-action redirect unauthenticated users to /signup/ rather than a follow or content endpoint. Clicking the like button, comment textarea, or 'Post' button all silently redirect to /signup/, harvesting sign-up intent under false interactive pretenses. (location: page.html:684,692,709,713)
social engineering
The 'AI Girlfriend' navigation link (http://camsoda.ai/?id=advfapcatai) uses HTTP (not HTTPS) and routes through an affiliate tracking ID. The label 'AI Girlfriend' is designed to exploit interest in AI companionship to drive affiliate traffic to a cam site. (location: page.html:631)
brand impersonation
An ad unit (lines 971-1011) impersonates the site's native content format by using the identical card layout, gradient avatar ring, username display, and 'See all content' CTA button as real creator posts. The 'AD' badge is small and easy to overlook, making the ad indistinguishable from organic content to casual users and automated agents crawling the feed. (location: page.html:971-1011)
hidden content
A fixed-position welcome bar (.wbar) is rendered with display:none by default and shown/hidden via localStorage state. It links to https://fapello.com/a/menu-1/ via a full-width clickable image, with a tiny close button (16px, 50% opacity). The bar reappears every 24 hours regardless of user dismissal. The destination URL /a/menu-1/ is opaque and likely an affiliate or ad redirect. (location: page.html:1704-1733)
malicious redirect
Two ad iframes are loaded from www.adxserve.com (different spelling from adxsrver.com in scripts — two distinct third-party ad domains) delivering banner ads via zoneid parameters. These iframes have allow='autoplay' which permits auto-playing media that can be used for audio-based social engineering or drive-by redirects within the iframe context. (location: page.html:571-576)
curl https://api.brin.sh/domain/fapello.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
fapello.com currently scores 41/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.