context safety score
A score of 54/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
3 deceptive links where visible host does not match destination host
hidden content
Site title and site description are hidden via CSS clip-path:inset(50%) and position:absolute, rendering them invisible to human visitors while remaining present in the DOM for crawlers and AI agents. This is a cloaking technique that can serve different content to automated readers vs. visual users. (location: page.html:28 — .site-branding .site-title, .site-description { clip-path:inset(50%); position:absolute })
hidden content
The listing thumbnail CSS applies margin-right:5500px, an extremely large margin value used as a layout hack to push content off-screen. While potentially a functional workaround, this technique can be exploited to hide content from visual users while keeping it accessible to DOM-parsing agents. (location: page.html:30 — .wpbdp-listing .listing-thumbnail { float:left; margin-right:5500px })
social engineering
A full-screen age-verification overlay (#evav-overlay-wrap) is rendered with display:none and uses high z-index (9999999999) to block page interaction. The overlay uses dark-pattern button styling (green confirm, red deny) and presents alarming legal-sounding warning text to pressure users into confirming age. This is a social engineering gate that normalizes blind consent to adult content access. (location: page.html:10,27 — #evav-overlay-wrap and #evav_confirm_age/#evav_not_confirm_age button styles)
malicious redirect
A third-party script is loaded from creative.rmhfrtnd.com (an obfuscated/non-descriptive domain) and immediately mounts a StripchatSpot widget directly onto document.body. Loading executable JavaScript from an unrecognized external domain with full DOM access constitutes a supply-chain risk and potential malicious redirect vector for AI agents following links or executing page scripts. (location: page.html:39-41 — src=https://creative.rmhfrtnd.com/widgets/Spot/lib.js; spot.mount(document.body))
social engineering
A sticky footer banner promotes 'Special Offer: Free Live Cams From FindCamGirl.com' linking to xrateduniversity.com — a domain whose name implies educational content but leads to an adult cam site. The deceptive framing ('Special Offer', 'Free') combined with a misleading domain name constitutes low-level social engineering. (location: page.html:32 — simpleBannerScriptParams banner_text linking to https://xrateduniversity.com/)
hidden content
The age-verification overlay text ('Please verify you are 18 years or older', warning language) is present in the DOM as hidden content (display:none overlay) that is not visible to users on page load but is extractable by AI agents parsing the DOM, potentially causing agents to interpret the page as posing legal/access warnings. (location: page-hidden.txt:1-2 — age gate warning text within hidden #evav-overlay-wrap element)
social engineering
Affiliate links to Chaturbate and Brazzers use image buttons labeled generically ('visit site') without disclosing the destination brand or affiliate relationship at the link level. The affiliate disclaimer is buried in the footer. Images are hotlinked from nichepornsites.com, obscuring the true affiliate relationship from DOM inspection. (location: page.html:41 — affiliate links to chaturbate.com/affiliates and landing.brazzersnetwork.com with images from nichepornsites.com)
curl https://api.brin.sh/domain/findcamgirl.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
findcamgirl.com currently scores 54/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.